Description
The lack of protections on alternate paths to access
control-protected assets (such as unprotected shadow registers
and other external facing unguarded interfaces) allows an
attacker to bypass existing protections to the asset that are
only performed against the primary path.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Confidentiality, Integrity, Availability, Access Control: Modify Memory, Read Memory, DoS: Resource Consumption (Other), Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity, Alter Execution Logic, Bypass Protection Mechanism, Quality Degradation
Potential Mitigations
Phase: Requirements
Effectiveness: Defense in Depth
Description:
Protect assets from accesses against all potential interfaces and alternate paths.
Phase: Architecture and Design
Effectiveness: Defense in Depth
Description:
Protect assets from accesses against all potential interfaces and alternate paths.
Phase: Implementation
Effectiveness: Defense in Depth
Description:
Protect assets from accesses against all potential interfaces and alternate paths.
CVE References
- CVE-2017-18293
- When GPIO is protected by blocking access
to corresponding GPIO resource registers,
protection can be bypassed by writing to the
corresponding banked GPIO registers instead.
- When GPIO is protected by blocking access
- CVE-2020-15483
- monitor device allows access to physical UART debug port without authentication
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...