This weakness can be found using automated static analysis once a developer has indicated which code paths are critical to protect.
CWE-1332 Base Estável
Improper Handling of Faults that Lead to Instruction Skips
This vulnerability occurs when a hardware device lacks or incorrectly implements the necessary circuitry or sensors to detect and respond to the skipping of critical security instructions during CPU…
Definição
What is CWE-1332?
This vulnerability occurs when a hardware device lacks or incorrectly implements the necessary circuitry or sensors to detect and respond to the skipping of critical security instructions during CPU execution.
Hardware can behave unpredictably under certain operating conditions, such as during electrical disturbances or when pushed beyond its normal specifications. These conditions can cause the CPU to skip crucial security instructions, effectively bypassing the logic they were meant to enforce. In practice, this often targets single conditional branch instructions that control security decisions—like password verification or firmware authentication—flipping the intended outcome if skipped.
Attackers exploit this by using fault injection techniques to deliberately induce these unstable operating conditions, making instruction skips happen more reliably and frequently than they would naturally. This allows them to manipulate security-critical decision points, such as bypassing authentication checks or altering firmware validation processes.
Impacto no mundo real
Real-world CVEs caused by CWE-1332
-
fault injection attack bypasses the verification mode, potentially allowing arbitrary code execution.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable Other
A smart card contains authentication credentials that are used as authorization to enter a building. The credentials are only accessible when a correct PIN is presented to the card.
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. Exemplo de código seguro
Secure Other
There are several ways this weakness could be fixed.
- 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 conditions What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-1332
- Architecture and Design Design strategies for ensuring safe failure if inputs, such as Vcc, are modified out of acceptable ranges.
- Architecture and Design Design strategies for ensuring safe behavior if instructions attempt to be skipped.
- Architecture and Design Identify mission critical secrets that should be wiped if faulting is detected, and design a mechanism to do the deletion.
- Implementation Add redundancy by performing an operation multiple times, either in space or time, and perform majority voting. Additionally, make conditional instruction timing unpredictable.
- Implementation Use redundant operations or canaries to detect and respond to faults.
- Implementation 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.
Sinais de deteção
How to detect CWE-1332
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.
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.
CWE-1332
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-1332?
Qual a gravidade do CWE-1332?
Que linguagens ou plataformas são afetadas pelo CWE-1332?
Como posso prevenir o CWE-1332?
Como é que o Plexicus deteta e corrige o CWE-1332?
Onde posso saber mais sobre o CWE-1332?
Frequently asked questions
O que é o CWE-1332?
This vulnerability occurs when a hardware device lacks or incorrectly implements the necessary circuitry or sensors to detect and respond to the skipping of critical security instructions during CPU execution.
Qual a gravidade do CWE-1332?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-1332?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, System on Chip.
Como posso prevenir o CWE-1332?
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.
Como é que o Plexicus deteta e corrige o CWE-1332?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1332 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-1332?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1332.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-1332
CWE-1384 Pai
Improper Handling of Physical or Environmental Conditions
This weakness occurs when a hardware device fails to manage unexpected physical or environmental situations, whether they happen naturally…
CWE-1247 Irmão
Improper Protection Against Voltage and Clock Glitches
This vulnerability occurs when a hardware device lacks proper physical safeguards against deliberate electrical manipulation. Without…
CWE-1261 Irmão
Improper Handling of Single Event Upsets
This vulnerability occurs when hardware logic fails to properly manage single-event upsets (SEUs), which are temporary bit flips caused by…
CWE-1351 Irmão
Improper Handling of Hardware Behavior in Exceptionally Cold Environments
This weakness occurs when a hardware device or its firmware lacks proper safeguards to maintain security functions when operated in…
Recursos
Further reading
- MITRE — CWE-1332 oficial https://cwe.mitre.org/data/definitions/1332.html
- An In-depth and Black-box Characterization of the Effects of Clock Glitches on 8-bit MCUs https://ieeexplore.ieee.org/document/6076473
- Experimental Analysis of the Electromagnetic Instruction Skip Fault Model https://ieeexplore.ieee.org/document/9081261
- Controlling PC on ARM using Fault Injection https://fdtc.deib.polimi.it/FDTC16/shared/FDTC-2016-session_2_1.pdf
- Attacking USB Gear with EMFI https://www.totalphase.com/media/pdf/whitepapers/Circuit_Cellar_TP.pdf
- On The Susceptibility of Texas Instruments SimpleLink Platform Microcontrollers to Non-Invasive Physical Attacks https://eprint.iacr.org/2022/328.pdf
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.