| Nature | Type | ID | Name |
|---|---|---|---|
| MemberOf | ViewView - a subset of CWE entries that provides a way of examining CWE content. The two main view structures are Slices (flat lists) and Graphs (containing relationships between entries). | 1432 | Weaknesses in the 2025 CWE Most Important Hardware Weaknesses List |
| HasMember | BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. | 1231 | Improper Prevention of Lock Bit Modification |
| HasMember | BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. | 1233 | Security-Sensitive Hardware Controls with Missing Lock Bit Protection |
| HasMember | BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. | 1244 | Internal Asset Exposed to Unsafe Debug Access Level or State |
| HasMember | BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. | 1272 | Sensitive Information Uncleared Before Debug/Power State Transition |
| HasMember | BaseBase - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. | 1431 | Driving Intermediate Cryptographic State/Results to Hardware Module Outputs |
Usage: PROHIBITED
Reason: Category
Rationale:
This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.Comments:
See member weaknesses of this category.| Submissions | ||
|---|---|---|
| Submission Date | Submitter | Organization |
|
2025年09月06日
(CWE 4.18, 2025年09月09日) |
CWE Content Team | MITRE |
| Contributions | ||
| Contribution Date | Contributor | Organization |
|
2025年08月20日
(CWE 4.18, 2025年09月09日) |
2025 MIHW Working Group | |
| Helped the CWE Team to define methodology and scoring algorithms; performed data analysis and mappings for Weakness Data Collection (WDC); and/or participated in Expert Poll 1 (EP1) or Expert Poll 2 (EP2). | ||
Use of the Common Weakness Enumeration (CWE™) and the associated references from this website are subject to the Terms of Use. CWE is sponsored by the U.S. Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA) and managed by the Homeland Security Systems Engineering and Development Institute (HSSEDI) which is operated by The MITRE Corporation (MITRE). Copyright © 2006–2025, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation.