Description
The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.
The operating conditions of hardware may change in ways that cause unexpected behavior to occur, including the skipping of security-critical CPU instructions. Generally, this can occur due to electrical disturbances or when the device operates outside of its expected conditions. In practice, application code may contain conditional branches that are security-sensitive (e.g., accepting or rejecting a user-provided password). These conditional branches are typically implemented by a single conditional branch instruction in the program binary which, if skipped, may lead to effectively flipping the branch condition - i.e., causing the wrong security-sensitive branch to be taken. This affects processes such as firmware authentication, password verification, and other security-sensitive decision points. Attackers can use fault injection techniques to alter the operating conditions of hardware so that security-critical instructions are skipped more frequently or more reliably than they would in a "natural" setting.
Potential Impact
Confidentiality, Integrity, Authentication
Bypass Protection Mechanism, Alter Execution Logic, Unexpected State
Demonstrative Examples
The card emits the credentials when a voltage anomaly is injected into the power line to the device at a particular time after providing an incorrect PIN to the card, causing the internal program to accept the incorrect PIN.add an internal filter or internal power supply in series with the power supply pin on the device
add sensing circuitry to reset the device if out of tolerance conditions are detected
add additional execution sensing circuits to monitor the execution order for anomalies and abort the action or reset the device under fault conditionsMitigations & Prevention
Design strategies for ensuring safe failure if inputs, such as Vcc, are modified out of acceptable ranges.
Design strategies for ensuring safe behavior if instructions attempt to be skipped.
Identify mission critical secrets that should be wiped if faulting is detected, and design a mechanism to do the deletion.
Add redundancy by performing an operation multiple times, either in space or time, and perform majority voting. Additionally, make conditional instruction timing unpredictable.
Use redundant operations or canaries to detect and respond to faults.
Ensure that fault mitigations are strong enough in practice. For example, a low power detection mechanism that takes 50 clock cycles to trigger at lower voltages may be an insufficient security mechanism if the instruction counter has already progressed with no other CPU activity occurring.
Detection Methods
- Automated Static Analysis Moderate — This weakness can be found using automated static analysis once a developer has indicated which code paths are critical to protect.
- Simulation / Emulation Moderate — This weakness can be found using automated dynamic analysis. Both emulation of a CPU with instruction skips, as well as RTL simulation of a CPU IP, can indicate parts of the code that are sensitive to faults due to instruction skips.
- Manual Analysis Moderate — This weakness can be found using manual (static) analysis. The analyst has security objectives that are matched against the high-level code. This method is less precise than emulation, especially if the analysis is done at the higher level language rather than at assembly level.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2019-15894 | fault injection attack bypasses the verification mode, potentially allowing arbitrary code execution. |
Related Weaknesses
Frequently Asked Questions
What is CWE-1332?
CWE-1332 (Improper Handling of Faults that Lead to Instruction Skips) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.
How can CWE-1332 be exploited?
Attackers can exploit CWE-1332 (Improper Handling of Faults that Lead to Instruction Skips) to bypass protection mechanism, alter execution logic, unexpected state. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-1332?
Key mitigations include: Design strategies for ensuring safe failure if inputs, such as Vcc, are modified out of acceptable ranges.
What is the severity of CWE-1332?
CWE-1332 is classified as a Base-level weakness (Medium abstraction). It has been observed in 1 real-world CVEs.