Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CAPEC-180:Exploiting Incorrectly Configured Access Control Security Levels
Attack Pattern ID:180
Version:v3.9
Attack Pattern Name:Exploiting Incorrectly Configured Access Control Security Levels
Abstraction:Standard
Status:Draft
Likelihood of Attack:High
Typical Severity:Medium
DetailsContent HistoryRelated WeaknessesReports
▼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.

▼Alternate Terms
▼Relationships
NatureTypeIDName
ChildOfM122Privilege Abuse
ParentOfD58Restful Privilege Elevation
ParentOfD679Exploitation of Improperly Configured or Implemented Memory Protections
ParentOfD680Exploitation of Improperly Controlled Registers
ParentOfD681Exploitation of Improperly Controlled Hardware Security Identifiers
ParentOfD702Exploiting Incorrect Chaining or Granularity of Hardware Debug Components
CanFollowS663Exploitation of Transient Instruction Execution
CanPrecedeS17Using Malicious Files
Nature: ChildOf
Type: Meta
ID: 122
Name: Privilege Abuse
Nature: ParentOf
Type: Detailed
ID: 58
Name: Restful Privilege Elevation
Nature: ParentOf
Type: Detailed
ID: 679
Name: Exploitation of Improperly Configured or Implemented Memory Protections
Nature: ParentOf
Type: Detailed
ID: 680
Name: Exploitation of Improperly Controlled Registers
Nature: ParentOf
Type: Detailed
ID: 681
Name: Exploitation of Improperly Controlled Hardware Security Identifiers
Nature: ParentOf
Type: Detailed
ID: 702
Name: Exploiting Incorrect Chaining or Granularity of Hardware Debug Components
Nature: CanFollow
Type: Standard
ID: 663
Name: Exploitation of Transient Instruction Execution
Nature: CanPrecede
Type: Standard
ID: 17
Name: Using Malicious Files
▼Execution Flow
Explore
1.

Survey

The attacker surveys the target application, possibly as a valid and authenticated user.

Technique
Spider the web site for all available links.
Brute force to guess all function names/action with different privileges.
Experiment
1.

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.

Technique
The attacker attempts authenticated access to targeted functions and data.
The attacker attempts unauthenticated access to targeted functions and data.
The attacker attempts indirect and side channel access to targeted functions and data.
Exploit
1.

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.

Technique
The attacker executes the function or accesses the data not authorized to them.
▼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.

▼Resources Required
None: No specialized resources are required to execute this type of attack.
▼Indicators
▼Consequences
ScopeLikelihoodImpactNote
IntegrityN/AModify DataN/A
ConfidentialityN/ARead DataN/A
AuthorizationN/AExecute Unauthorized CommandsRun Arbitrary Code
AuthorizationN/AGain PrivilegesN/A
Access ControlAuthorizationN/ABypass Protection MechanismN/A
AvailabilityN/AUnreliable ExecutionN/A
Scope: Integrity
Likelihood: N/A
Impact: Modify Data
Note: N/A
Scope: Confidentiality
Likelihood: N/A
Impact: Read Data
Note: N/A
Scope: Authorization
Likelihood: N/A
Impact: Execute Unauthorized Commands
Note: Run Arbitrary Code
Scope: Authorization
Likelihood: N/A
Impact: Gain Privileges
Note: N/A
Scope: Access Control, Authorization
Likelihood: N/A
Impact: Bypass Protection Mechanism
Note: N/A
Scope: Availability
Likelihood: N/A
Impact: Unreliable Execution
Note: N/A
▼Mitigations
Design: Configure the access control correctly.
▼Example Instances
▼Related Weaknesses
IDName
CWE-1190DMA Device Enabled Too Early in Boot Phase
CWE-1191On-Chip Debug and Test Interface With Improper Access Control
CWE-1193Power-On of Untrusted Execution Core Before Enabling Fabric Access Control
CWE-1220Insufficient Granularity of Access Control
CWE-1268Policy Privileges are not Assigned Consistently Between Control and Data Agents
CWE-1280Access Control Check Implemented After Asset is Accessed
CWE-1297Unprotected Confidential Information on Device is Accessible by OSAT Vendors
CWE-1311Improper Translation of Security Attributes by Fabric Bridge
CWE-1315Improper Setting of Bus Controlling Capability in Fabric End-point
CWE-1318Missing Support for Security Features in On-chip Fabrics or Buses
CWE-1320Improper Protection for Outbound Error Messages and Alert Signals
CWE-1321Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
CWE-732Incorrect Permission Assignment for Critical Resource
ID: CWE-1190
Name: DMA Device Enabled Too Early in Boot Phase
ID: CWE-1191
Name: On-Chip Debug and Test Interface With Improper Access Control
ID: CWE-1193
Name: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control
ID: CWE-1220
Name: Insufficient Granularity of Access Control
ID: CWE-1268
Name: Policy Privileges are not Assigned Consistently Between Control and Data Agents
ID: CWE-1280
Name: Access Control Check Implemented After Asset is Accessed
ID: CWE-1297
Name: Unprotected Confidential Information on Device is Accessible by OSAT Vendors
ID: CWE-1311
Name: Improper Translation of Security Attributes by Fabric Bridge
ID: CWE-1315
Name: Improper Setting of Bus Controlling Capability in Fabric End-point
ID: CWE-1318
Name: Missing Support for Security Features in On-chip Fabrics or Buses
ID: CWE-1320
Name: Improper Protection for Outbound Error Messages and Alert Signals
ID: CWE-1321
Name: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
ID: CWE-732
Name: Incorrect Permission Assignment for Critical Resource
▼Taxonomy Mappings
Taxonomy NameEntry IDEntry Name
ATTACK1574.010Hijack Execution Flow: Services File Permissions Weaknesses
Taxonomy Name: ATTACK
Entry ID: 1574.010
Entry Name: Hijack Execution Flow: Services File Permissions Weaknesses
▼Notes
▼References
Reference ID: REF-29
Title: Share Library Call Redirection Via ELF PLT Infection
Author: Silvio Cesare
Publication:
Phrack Magazine
Publisher:
Edition:Issue 56
URL:http://phrack.org/issues/56/7.html
URL Date:
Day:N/A
Month:N/A
Year:2000
Reference ID: REF-30
Title: OWASP Top 10 2007
Author:
Publication:
Publisher:The Open Web Application Security Project (OWASP)
Edition:2007
URL:https://www.owasp.org/www-pdf-archive/OWASP_Top_10_2007.pdf
URL Date:
Day:N/A
Month:N/A
Year:N/A
Details not found