CWE-1332: Improper Handling of Faults that Lead to Instruction Skips

BaseStable

The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms
Not OS-Specific

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1332 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1332, Improper Handling of Faults that Lead to Instruction Skips, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Improper Handling of Faults that Lead to Instruction Skips during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; documented detection approaches include Automated Static Analysis, Simulation / Emulation, and Manual Analysis; recorded impacts include Bypass Protection Mechanism, Alter Execution Logic, and Unexpected State. Use these source-defined anchors to turn CWE-1332 into implementation, review, and verification checks for the affected component.

CWE-1332: Improper Handling of Faults that Lead to Instruction SkipsMITRE CWE

Triage CWE-1332 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1332, Improper Handling of Faults that Lead to Instruction Skips, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1332

Apply MITRE's full root-cause mapping guidance when using CWE-1332, Improper Handling of Faults that Lead to Instruction Skips. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-1332 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1332, Improper Handling of Faults that Lead to Instruction Skips. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-1332: Improper Handling of Faults that Lead to Instruction Skips?+

CWE-1332: Improper Handling of Faults that Lead to Instruction Skips is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Handling of Faults that Lead to Instruction Skips?+

If exploited, CWE-1332 (Improper Handling of Faults that Lead to Instruction Skips) it can compromise Confidentiality, Integrity and Authentication, leading to outcomes such as Bypass Protection Mechanism, Alter Execution Logic and Unexpected State.

How do you prevent or mitigate Improper Handling of Faults that Lead to Instruction Skips?+

Recommended mitigations for CWE-1332 include: 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.

How is Improper Handling of Faults that Lead to Instruction Skips detected?+

CWE-1332 can be detected using Automated Static Analysis, Simulation / Emulation and Manual Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Handling of Faults that Lead to Instruction Skips?+

CWE-1332 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Handling of Faults that Lead to Instruction Skips?+

MITRE documents real CVEs mapped to CWE-1332, including CVE-2019-15894. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1332 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement