CWE-1244
Internal Asset Exposed to Unsafe Debug Access Level or State
Description
The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents.
{"xhtml:p":["Debug authorization can have multiple levels of\n\t access, defined such that different system internal assets\n\t are accessible based on the current authorized debug\n\t level. Other than debugger authentication (e.g., using\n\t passwords or challenges), the authorization can also be\n\t based on the system state or boot stage. For example, full\n\t system debug access might only be allowed early in boot\n\t after a system reset to ensure that previous session data is\n\t not accessible to the authenticated debugger."]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Read Memory
Scope
Impact
Modify Memory
Scope
Impact
Gain Privileges or Assume Identity, Bypass Protection Mechanism
Potential Mitigations
For security-sensitive assets accessible over debug/test interfaces, only allow trusted agents.
Apply blinding [REF-1219] or masking techniques in strategic areas.
Add shielding or tamper-resistant protections to the device, which increases the difficulty and cost for accessing debug/test interfaces.
CVE-2019-18827After ROM code execution, JTAG access is disabled. But before the ROM code is executed, JTAG access is possible, allowing a user full system access. This allows a user to modify the boot flow and successfully bypass the secure-boot process.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now