A hardware weakness that reaches silicon cannot be patched like software: it can only be mitigated in microcode, firmware or the operating system, often at a performance cost, or the part must be replaced. MITRE's Common Weakness Enumeration (CWE) has a dedicated view for this problem, CWE-1194 Hardware Design, which organises hardware weaknesses around the concepts chip and system designers actually work with: debug interfaces, lock bits, memory ranges, power and clock control, and cryptographic primitives. This guide explains how the view is structured, walks through the weaknesses that matter most, and shows how design, verification and procurement teams can use the IDs in requirements, reviews and vulnerability reports. It is for SoC and FPGA designers, hardware security verification engineers, product security teams and buyers who need to ask suppliers the right questions. For the trust anchor these weaknesses most often undermine, see the Hardware Root of Trust Guide.
Key takeaways
- CWE-1194 is a navigation view for hardware designers: in CWE 4.20 it groups hardware weaknesses into 12 categories, from Manufacturing and Life Cycle Management (CWE-1195) to Cross-Cutting Problems (CWE-1208).
- Start with the 12 most important: the 2021 Most Important Hardware Weaknesses list (view CWE-1343), selected by the Hardware CWE Special Interest Group, is the practical short list for reviews.
- Debug and lock bits dominate: unprotected JTAG and debug states (CWE-1191, CWE-1244) and modifiable or missing lock bits (CWE-1231, CWE-1233) appear again and again in real silicon.
- Software can attack hardware: CWE-1256 covers power and clock interfaces exposed to software, with observed examples such as Plundervolt (CVE-2019-11157) and PLATYPUS (CVE-2020-8694).
- Verification must cover pre-silicon and post-silicon: CWE entries call for architecture review, pre-silicon checks and post-silicon testing that debug interfaces are not open by default.
What the CWE-1194 view is and how it differs
CWE is the MITRE-maintained catalogue of weakness types: the root-cause classes behind individual CVE records. Most practitioners know it through the software-centric CWE Top 25 (see the CWE Top 25 Guide). The hardware entries live in the same catalogue, but the CWE-1194 view arranges them for a different audience. MITRE states the view's objective as organising weaknesses around concepts frequently used or encountered in hardware design, and names two audiences: hardware designers, who use it to find likely mistakes in specific areas of their IP, and educators teaching hardware security.
- Weakness, not vulnerability: a CWE ID names a class of mistake, such as "Improper Prevention of Lock Bit Modification". A CVE names a specific flaw in a specific product. One CVE is usually mapped to one or more CWEs. See the CVE, CWE and CPE Guide.
- Design-phase language: hardware entries describe modes of introduction such as Architecture and Design or Implementation, and detection methods such as pre-silicon and post-silicon testing, which match the chip development life cycle.
- Linked to attack patterns: entries reference CAPEC attack patterns, for example CAPEC-624 Hardware Fault Injection and CAPEC-663 Exploitation of Transient Instruction Execution, which helps threat modelling.
The 12 categories of the hardware view
| Category | Name | Typical design area |
|---|---|---|
| CWE-1195 | Manufacturing and Life Cycle Management Concerns | Provisioning, test modes left in production, decommissioning |
| CWE-1196 | Security Flow Issues | Secure boot and state machine flows |
| CWE-1197 | Integration Issues | Combining third-party IP blocks on an SoC |
| CWE-1198 | Privilege Separation and Access Control Issues | Bus access control, security identifiers, isolation |
| CWE-1199 | General Circuit and Logic Design Concerns | Lock bits, register defaults, logic errors |
| CWE-1201 | Core and Compute Issues | Processor pipelines, speculation, microarchitecture |
| CWE-1202 | Memory and Storage Issues | Memory protection ranges, boot memory, retention |
| CWE-1203 | Peripherals, On-chip Fabric, and Interface/IO Problems | Interconnect, DMA, external interfaces |
| CWE-1205 | Security Primitives and Cryptography Issues | Key storage, RNGs, crypto engines |
| CWE-1206 | Power, Clock, Thermal, and Reset Concerns | Voltage and frequency control, reset behaviour |
| CWE-1207 | Debug and Test Problems | JTAG, scan chains, debug unlock |
| CWE-1208 | Cross-Cutting Problems | Firmware updateability and issues spanning several areas |
These are the categories shown in CWE 4.20; check the live view before building a taxonomy on it, because CWE releases add and rename entries. The categories give a review checklist structure: a design review can walk an SoC block diagram and ask, for each block, which categories apply.
The 2021 Most Important Hardware Weaknesses
View CWE-1343 holds the 12 weaknesses chosen by the Hardware CWE Special Interest Group for the 2021 list. Unlike the software Top 25, it is not derived from CVE frequency, so treat it as an expert-curated priority list.
| CWE | Name | What goes wrong | Primary control |
|---|---|---|---|
| CWE-1189 | Improper Isolation of Shared Resources on System-on-a-Chip (SoC) | Trusted and untrusted agents share a resource without isolation | Partition resources per security domain |
| CWE-1191 | On-Chip Debug and Test Interface With Improper Access Control | JTAG or test modes reachable without authorisation | Disable or authenticate debug; clear secrets on entering debug |
| CWE-1231 | Improper Prevention of Lock Bit Modification | A lock bit can be cleared after it is set | Sticky, write-once lock logic until reset |
| CWE-1233 | Security-Sensitive Hardware Controls with Missing Lock Bit Protection | Critical registers have no lock at all | Lock coverage review of all security registers |
| CWE-1240 | Use of a Cryptographic Primitive with a Risky Implementation | Custom or weak cryptographic hardware | Use vetted algorithms and implementations |
| CWE-1244 | Internal Asset Exposed to Unsafe Debug Access Level or State | Debug level grants access to assets it should not | Map assets to debug levels and test each |
| CWE-1256 | Improper Restriction of Software Interfaces to Hardware Features | Software controls voltage, clock or power telemetry | Access control on physical operating condition controls |
| CWE-1260 | Improper Handling of Overlap Between Protected Memory Ranges | Overlapping ranges let a lower-privilege range cover a protected one | Priority rules and checks for overlaps |
| CWE-1272 | Sensitive Information Uncleared Before Debug/Power State Transition | Secrets survive into debug or low-power states | Clear assets on every state transition |
| CWE-1274 | Improper Access Control for Volatile Memory Containing Boot Code | Boot code in RAM can be modified before execution | Lock boot memory regions from untrusted agents |
| CWE-1277 | Firmware Not Updateable | No way to patch firmware | Authenticated, integrity-checked update path |
| CWE-1300 | Improper Protection of Physical Side Channels | Power, EM or acoustic leakage reveals secrets | Masking, blinding, shielding |
Weakness deep dives
Debug and test interfaces (CWE-1191, CWE-1244, CWE-1272)
CWE-1191 lists the consequences of an unprotected debug and test interface as high-likelihood reading of memory, execution of unauthorised code, modification of memory and bypass of protection mechanisms. The mitigations are to disable JTAG or require authentication and authorisation, make the authentication logic resistant to timing attacks, and clear security-sensitive registers such as keys on entering debug mode. Its observed example, CVE-2019-18827, describes a JTAG interface left enabled during ROM code execution, where a race condition allowed extraction of encryption keys. The detection guidance is explicit that hiding register documentation is not enough, and that both pre-silicon and post-silicon testing should confirm the interface is not open by default.
Lock bits and register protection (CWE-1231, CWE-1233)
Security configuration registers, such as memory protection settings or fuse controller settings, are normally set by early boot code and then locked. CWE-1231 covers a lock that can be undone; CWE-1233 covers a register that was never locked. Both let later, less trusted software change security settings. The fix is design discipline: a register inventory that records, for each security-relevant register, its lock bit, who may write it and when the lock clears (normally only on reset).
Software-reachable physical controls (CWE-1256)
Modern processors let software manage voltage and frequency and read power telemetry. CWE-1256 lists Plundervolt (CVE-2019-11157), where improper voltage-setting checks on some Intel processors could let a privileged local user escalate privileges or disclose information, PLATYPUS (CVE-2020-8694) and CVE-2020-8695 on the RAPL power interface, CVE-2020-12912 on an AMD RAPL extension, and CVE-2015-0565, where Google Native Client allowed the CLFLUSH instruction and made Rowhammer possible. It maps to CAPEC-624 Hardware Fault Injection. The lesson for designers is that any software interface that changes physical operating conditions is a security boundary.
Transient execution (CWE-1037, CWE-1420 family)
CWE-1037 "Processor Optimization Removal or Modification of Security-critical Code" cites Spectre (CVE-2017-5715, CVE-2017-5753) and Meltdown (CVE-2017-5754) as observed examples. CWE-1420 "Exposure of Sensitive Information during Transient Execution" and its children CWE-1421, CWE-1422 and CWE-1423 now describe the transient execution classes more precisely: leakage through shared microarchitectural structures, through incorrect data forwarding, and through shared predictor state. Use the 1420 family for new transient execution findings.
Physical side channels (CWE-1300)
CWE-1300 covers leakage through power consumption, electromagnetic emissions or sound. Its observed examples include CVE-2021-3011, an electromagnetic side channel in microcontrollers allowing private key extraction, and CVE-2019-14353, where a hardware wallet's power draw varied with the number of lit pixels and exposed PINs. Mitigations are blinding or masking in cryptographic implementations during design and shielding or tamper resistance in implementation. See the Fault Injection Attacks Guide and the TEMPEST and Emanations Security Guide.
Firmware updateability (CWE-1277)
CWE-1277 is where hardware design meets fleet operations. Its observed example, CVE-2020-9054, was an OS command injection in Zyxel NAS devices that was actively exploited for a botnet, and some affected products were end of support and could not be patched. CISA added CVE-2020-9054 to the Known Exploited Vulnerabilities catalogue on 25 March 2022. The mitigation set spans requirements (specify authenticated, integrity-checked updates), design and implementation. See the Firmware and Boot Security Guide.
Using hardware CWEs across the life cycle
- Requirements: write security requirements against CWE IDs, for example "debug access shall require authentication (CWE-1191)" and "all security configuration registers shall be lockable until reset (CWE-1233)". This gives verification a precise target.
- Threat modelling: for each IP block, list the applicable CWE-1194 categories and the CAPEC patterns linked from their entries.
- Architecture review: walk asset-to-debug-level mappings (CWE-1244), memory range priority rules (CWE-1260) and state transitions (CWE-1272) with the architects.
- Pre-silicon verification: turn each requirement into a property or test in simulation, emulation or formal verification, and run directed tests that try to change locked registers.
- Post-silicon validation: confirm on real parts that debug ports are closed or authenticated in production life cycle states and that fault and side-channel resistance meet the target.
- Vulnerability handling: when a flaw is found after release, map it to the most specific CWE in the advisory and the CVE record, and decide whether microcode, firmware, OS or configuration mitigation is possible.
- Feedback: track which CWEs recur across products and feed them back into design rules and IP selection.
Choosing where to invest: designers, integrators and buyers
| Role | Most relevant CWEs | What to do |
|---|---|---|
| SoC or IP designer | 1189, 1191, 1231, 1233, 1260, 1274 | Design rules, register inventory, pre-silicon properties |
| System integrator or OEM | 1191, 1244, 1277, 1256 | Confirm debug is locked in production, firmware update path exists, power controls restricted |
| Cryptographic module or secure element vendor | 1240, 1300, 1272 | Side-channel and fault testing, use of vetted implementations |
| Enterprise buyer | 1277, 1191, 1037 and 1420 family | Ask for updateability, debug lock state and transient execution mitigations in supplier questionnaires |
Small hardware teams should start with the 12 weaknesses in CWE-1343 and the debug and test category. Larger silicon organisations can map their full verification plan to all categories of CWE-1194 and measure coverage. Buyers can ask suppliers for a hardware bill of materials and which CWE classes were tested; see the Hardware and Firmware SBOM Guide.
Where identity fits
Many hardware weaknesses are attacks on device identity. Debug access that bypasses lock bits can read the device's private keys, side channels recover keys from secure elements, and an unprotected boot memory can change the code that later attests to the device's identity. When a device's key is extractable, every certificate and workload credential built on it is weaker than it looks. See the IoT Device Identity with TPM and DICE Guide.
Detection and measurement
- Requirement coverage: share of CWE-1343 weaknesses with a written requirement and at least one verification test for each product.
- Lock coverage: share of security-relevant registers with a verified lock bit.
- Debug state verification: share of production life cycle states in which post-silicon tests confirmed debug is closed or authenticated.
- Escape rate: number of hardware CWEs found after tape-out or after release, by category.
- Advisory quality: share of your hardware security advisories mapped to a specific hardware CWE rather than a generic class.
Framework mapping
| Framework | Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev. 5 | SA-8, SA-17 | Security engineering principles; developer security architecture and design |
| NIST SP 800-53 Rev. 5 | SA-11 | Developer testing and evaluation, including pre-silicon and post-silicon tests |
| NIST SP 800-53 Rev. 5 | SI-7, SR-4, SR-11 | Firmware integrity; provenance; component authenticity |
| NIST CSF 2.0 | ID.RA-01, ID.RA-08, PR.PS-02 | Vulnerabilities identified; disclosure handling; firmware maintained or replaced |
| MITRE ATT&CK v20 | T1542.001, T1495, T1200 | System firmware persistence; firmware corruption; hardware additions |
| CAPEC | CAPEC-624, CAPEC-663, CAPEC-180 | Hardware fault injection; transient instruction execution; misconfigured access control levels |
Common failure patterns
- Security by obscurity on debug: relying on undocumented registers or test modes, which CWE-1191 says is not sufficient.
- Locks that unlock: a lock bit implemented as an ordinary writable register, so later software clears it (CWE-1231).
- Third-party IP assumed secure: integration of licensed blocks without checking their isolation and debug behaviour (CWE-1197 category).
- Testing only in simulation: pre-silicon tests pass, but fused production parts still expose debug in some life cycle states.
- No update path: products shipped with firmware that cannot be updated, leaving known flaws permanent, as CWE-1277's Zyxel example shows.
- Generic CWE mapping: advisories that map a hardware flaw to a broad software CWE, so trend analysis and design feedback miss it.
Practitioner checklist
- Adopt CWE-1194 categories as the structure of your hardware security design review.
- Write requirements and tests for all 12 weaknesses in CWE-1343 for every new SoC or board.
- Keep a register inventory with lock bits, writers and reset behaviour for every security register.
- Map every asset to the debug levels that may access it, and test each mapping on silicon.
- Restrict software access to voltage, frequency and power telemetry interfaces.
- Require an authenticated, integrity-checked firmware update path in product requirements.
- Test cryptographic hardware for side-channel and fault resistance against a defined attacker model.
- Map post-release hardware flaws to the most specific hardware CWE and feed them back into design rules.
Standards and references
- MITRE CWE: CWE-1194 Hardware Design view
- MITRE CWE: CWE-1343 Weaknesses in the 2021 CWE Most Important Hardware Weaknesses List
- MITRE CWE: CWE-1191 On-Chip Debug and Test Interface With Improper Access Control
- MITRE CWE: CWE-1256 Improper Restriction of Software Interfaces to Hardware Features
- MITRE CWE: CWE-1420 Exposure of Sensitive Information during Transient Execution
- MITRE CWE: CWE-1300 Improper Protection of Physical Side Channels
- MITRE CWE: CWE-1277 Firmware Not Updateable
- CISA: Known Exploited Vulnerabilities Catalog
Related NHI Mgmt Group resources: Hardware Root of Trust Guide · Hardware Trojans and Chip Supply Chain Guide · CWE Top 25 Guide · Firmware and Boot Security Guide