CWE Glossary Definition |
👁 x
|
CWE CATEGORY: Cross-Cutting Problems
|
Category ID: 1208
Vulnerability Mapping:
PROHIBITED
This CWE ID must not be used to map to real-world vulnerabilities
|
Weaknesses in this category can arise in multiple areas of hardware design or can apply to a wide cross-section of components.
| Nature |
Type |
ID |
Name |
| MemberOf |
👁 View View - 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). |
1194 |
Hardware Design
|
| HasMember |
👁 Base Base - 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. |
440 |
Expected Behavior Violation
|
| HasMember |
👁 Base Base - 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. |
1053 |
Missing Documentation for Design
|
| HasMember |
👁 Class Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource. |
1059 |
Insufficient Technical Documentation
|
| HasMember |
👁 Class Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource. |
1263 |
Improper Physical Access Control
|
| HasMember |
👁 Base Base - 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. |
1277 |
Firmware Not Updateable
|
| HasMember |
👁 Base Base - 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. |
1301 |
Insufficient or Incomplete Data Removal within Hardware Component
|
| HasMember |
👁 Base Base - 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. |
1329 |
Reliance on Component That is Not Updateable
|
| HasMember |
👁 Class Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource. |
1357 |
Reliance on Insufficiently Trustworthy Component
|
| HasMember |
👁 Base Base - 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. |
1429 |
Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
|
👁 +
Vulnerability Mapping Notes
|
Usage:
PROHIBITED
(this CWE ID must not be used to map to real-world vulnerabilities)
|
|
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 |
2019-12-27
(CWE 4.0, 2020-02-24)
|
CWE Content Team |
MITRE |
👁 + Modifications |
| Modification Date |
Modifier |
Organization |
2025-04-03
(CWE 4.17, 2025-04-03)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
2023-06-29
(CWE 4.12, 2023-06-29)
|
CWE Content Team |
MITRE |
|
updated Mapping_Notes
|
2023-04-27
(CWE 4.11, 2023-04-27)
|
CWE Content Team |
MITRE |
|
updated Mapping_Notes
|
2023-01-31
(CWE 4.10, 2023-01-31)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
2022-10-13
(CWE 4.9, 2022-10-13)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
2022-04-28
(CWE 4.7, 2022-04-28)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
2020-08-20
(CWE 4.2, 2020-08-20)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
2020-06-25
(CWE 4.1, 2020-06-25)
|
CWE Content Team |
MITRE |
|
updated Relationships
|
More information is available — Please edit the custom filter or select a different filter.
|