CWE-1248: Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
The security-sensitive hardware module contains semiconductor defects.
Last updated
Overview
A semiconductor device can fail for various reasons. While some are manufacturing and packaging defects, the rest are due to prolonged use or usage under extreme conditions. Some mechanisms that lead to semiconductor defects include encapsulation failure, die-attach failure, wire-bond failure, bulk-silicon defects, oxide-layer faults, aluminum-metal faults (including electromigration, corrosion of aluminum, etc.), and thermal/electrical stress. These defects manifest as faults on chip-internal signals or registers, have the effect of inputs, outputs, or intermediate signals being always 0 or always 1, and do not switch as expected.
Common consequences
What can happen when CWE-1248 is exploited.
DoS: Instability
Affects: Availability, Access Control
If such faults occur in security-sensitive hardware modules, the security objectives of the hardware module may be compromised.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-1248, grouped by where in the lifecycle they apply.
While semiconductor-manufacturing companies implement several mechanisms to continuously improve the semiconductor manufacturing process to ensure reduction of defects, some defects can only be fixed after manufacturing. Post-manufacturing testing of silicon die is critical. Fault models such as stuck-at-0 or stuck-at-1 must be used to develop post-manufacturing test cases and achieve good coverage. Once the silicon packaging is done, extensive post-silicon testing must be performed to ensure that hardware logic implementing security functionalities is defect-free.
Operating the hardware outside device specification, such as at extremely high temperatures, voltage, etc., accelerates semiconductor degradation and results in defects. When these defects manifest as faults in security-critical, hardware modules, it results in compromise of security guarantees. Thus, operating the device within the specification is important.
Code examples
Illustrative examples from MITRE showing how the weakness appears in code.
The network-on-chip implements a firewall for access control to peripherals from all IP cores capable of mastering transactions.
Vulnerable example
A manufacturing defect in this logic manifests itself as a logical fault, which always sets the output of the filter to "allow" access.Post-manufacture testing must be performed to ensure that hardware logic implementing security functionalities is defect-free.
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-1248.
- What is CWE-1248?
- The security-sensitive hardware module contains semiconductor defects.
- How do you prevent CWE-1248?
- While semiconductor-manufacturing companies implement several mechanisms to continuously improve the semiconductor manufacturing process to ensure reduction of defects, some defects can only be fixed after manufacturing. Post-manufacturing testing of silicon die is critical. Fault models such as stuck-at-0 or stuck-at-1 must be used to develop post-manufacturing test cases and achieve good coverage. Once the silicon packaging is done, extensive post-silicon testing must be performed to ensure that hardware logic implementing security functionalities is defect-free.
- What are the consequences of CWE-1248?
- Exploiting CWE-1248 can lead to: DoS: Instability.
References
- MITRE CWE definition (CWE-1248) (opens in a new tab)
- CWE-1248 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-1248
Get alerted the moment a new CWE-1248 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.