VariantDraft

CWE-1239Improper Zeroization of Hardware Register

Category: other

Description

The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes. Hardware logic operates on data stored in registers local to the hardware block. Most hardware IPs, including cryptographic accelerators, rely on registers to buffer I/O, store intermediate values, and interface with software. The result of this is that sensitive information, such as passwords or encryption keys, can exist in locations not transparent to the user of the hardware logic. When a different entity obtains access to the IP due to a change in operating mode or conditions, the new entity can extract information belonging to the previous user if no mechanisms are in place to clear register contents. It is important to clear information stored in the hardware if a physical attack on the product is detected, or if the user of the hardware block changes. The process of clearing register contents in a hardware IP is referred to as zeroization in standards for cryptographic hardware modules such as FIPS-140-2 [REF-267].

Common consequences· 1

  • Confidentiality — Varies by Context
    The consequences will depend on the information disclosed due to the vulnerability.

Potential mitigations· 1

  • [Architecture and Design]Every register potentially containing sensitive information must have a policy specifying how and when information is cleared, in addition to clarifying if it is the responsibility of the hardware logic or IP user to initiate the zeroization procedure at the appropriate time.

Related CAPEC attack patterns· 4

CAPEC-150CAPEC-204CAPEC-37CAPEC-545

References

  1. https://cwe.mitre.org/data/definitions/1239.html

Exploits (incoming)4

TypeTargetConfidenceTier
AttackPatternCollect Data from Common Resource Locationscapec-150100%live
AttackPatternRetrieve Embedded Sensitive Datacapec-37100%live
AttackPatternLifting Sensitive Data Embedded in Cachecapec-204100%live
AttackPatternPull Data from System Resourcescapec-545100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Driving Intermediate Cryptographic State/Results to Hardware Module Outputs
CWE
Incorrect Register Defaults or Module Parameters
CWE
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
CWE
Failure to Disable Reserved Bits
CWE
Improper Access Control for Register Interface
CWE
Insufficient Granularity of Address Regions Protected by Register Locks
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.