CAPECattack pattern
CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels
Medium
Official page ↗
- Abstraction
- Standard
- Status
- Draft
- Likelihood of attack
- High
- Typical severity
- Medium
- CAPEC version
- 3.9
Description
An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
Extended description
Most commonly, attackers would take advantage of controls that provided too little protection for sensitive activities in order to perform actions that should be denied to them. In some circumstances, an attacker may be able to take advantage of overly restrictive access control policies, initiating denial of services (if an application locks because it unexpectedly failed to be granted access) or causing other legitimate actions to fail due to security. The latter class of attacks, however, is usually less severe and easier to detect than attacks based on inadequate security restrictions. This attack pattern differs from CAPEC 1, "Accessing Functionality Not Properly Constrained by ACLs" in that the latter describes attacks where sensitive functionality lacks access controls, where, in this pattern, the access control is present, but incorrectly configured.
Execution flow
1. [Explore] [Survey] The attacker surveys the target application, possibly as a valid and authenticated user.
2. [Experiment] [Identify weak points in access control configurations] The attacker probes the access control for functions and data identified in the Explore phase to identify potential weaknesses in how the access controls are configured.
3. [Exploit] [Access the function or data bypassing the access control] The attacker executes the function or accesses the data identified in the Explore phase bypassing the access control.
Prerequisites
• The target must apply access controls, but incorrectly configure them. However, not all incorrect configurations can be exploited by an attacker. If the incorrect configuration applies too little security to some functionality, then the attacker may be able to exploit it if the access control would be the only thing preventing an attacker's access and it no longer does so. If the incorrect configuration applies too much security, it must prevent legitimate activity and the attacker must be able to force others to require this activity..
Skills required
• [Low] In order to discover unrestricted resources, the attacker does not need special tools or skills. They only have to observe the resources or access mechanisms invoked as each action is performed and then try and access those access mechanisms directly.
Consequences
• Integrity: Modify Data
• Confidentiality: Read Data
• Authorization: Execute Unauthorized Commands
• Authorization: Gain Privileges
• Access Control, Authorization: Bypass Protection Mechanism
• Availability: Unreliable Execution
Mitigations
• Design: Configure the access control correctly.
Related
Att&ck technique · MITRE ATT&CK (1)
- T1574.010 Services File Permissions Weakness sub-technique
Can precede · CAPEC (1)
- CAPEC-17 Using Malicious Files attack pattern
Child of · CAPEC (1)
- CAPEC-122 Privilege Abuse attack pattern
Weakness · CWE (13)
- CWE-1190 DMA Device Enabled Too Early in Boot Phase weakness
- CWE-1191 On-Chip Debug and Test Interface With Improper Access Control weakness
- CWE-1193 Power-On of Untrusted Execution Core Before Enabling Fabric Access Control weakness
- CWE-1220 Insufficient Granularity of Access Control weakness
- CWE-1268 Policy Privileges are not Assigned Consistently Between Control and Data Agents weakness
- CWE-1280 Access Control Check Implemented After Asset is Accessed weakness
- CWE-1297 Unprotected Confidential Information on Device is Accessible by OSAT Vendors weakness
- CWE-1311 Improper Translation of Security Attributes by Fabric Bridge weakness
- CWE-1315 Improper Setting of Bus Controlling Capability in Fabric End-point weakness
- CWE-1318 Missing Support for Security Features in On-chip Fabrics or Buses weakness
- CWE-1320 Improper Protection for Outbound Error Messages and Alert Signals weakness
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes weakness
- CWE-732 Incorrect Permission Assignment for Critical Resource weakness
Referenced by CAPEC · child of (5)
- CAPEC-58 Restful Privilege Elevation attack pattern
- CAPEC-679 Exploitation of Improperly Configured or Implemented Memory Protections attack pattern
- CAPEC-680 Exploitation of Improperly Controlled Registers attack pattern
- CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers attack pattern
- CAPEC-702 Exploiting Incorrect Chaining or Granularity of Hardware Debug Components attack pattern
Referenced by CAPEC · peer of (1)
- CAPEC-663 Exploitation of Transient Instruction Execution attack pattern
Referenced by CWE · attack pattern (13)
- CWE-1190 DMA Device Enabled Too Early in Boot Phase weakness
- CWE-1191 On-Chip Debug and Test Interface With Improper Access Control weakness
- CWE-1193 Power-On of Untrusted Execution Core Before Enabling Fabric Access Control weakness
- CWE-1220 Insufficient Granularity of Access Control weakness
- CWE-1268 Policy Privileges are not Assigned Consistently Between Control and Data Agents weakness
- CWE-1280 Access Control Check Implemented After Asset is Accessed weakness
- CWE-1297 Unprotected Confidential Information on Device is Accessible by OSAT Vendors weakness
- CWE-1311 Improper Translation of Security Attributes by Fabric Bridge weakness
- CWE-1315 Improper Setting of Bus Controlling Capability in Fabric End-point weakness
- CWE-1318 Missing Support for Security Features in On-chip Fabrics or Buses weakness
- CWE-1320 Improper Protection for Outbound Error Messages and Alert Signals weakness
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes weakness
- CWE-732 Incorrect Permission Assignment for Critical Resource weakness