Modes Of Introduction
Architecture and Design : This weakness can arise if design decisions are made that do not align with the intended physical protection of the product
Manufacturing : While the architecture and design phase of the product may have accurately met the intended robustness for product physical protections, this phase may introduce the weakness through errors in physically manufacturing the product.
Applicable Platforms
Language
Class: Not Language-Specific (Undetermined)
Operating Systems
Class: Not OS-Specific (Undetermined)
Architectures
Class: Not Architecture-Specific (Undetermined)
Technologies
Class: Not Technology-Specific (Undetermined)
Common Consequences
Scope |
Impact |
Likelihood |
Confidentiality Integrity Access Control | Varies by Context | |
Potential Mitigations
Phases : Architecture and Design
Specific protection requirements depend strongly on contextual factors including the level of acceptable risk associated with compromise to the product's protection mechanism. Designers could incorporate anti-tampering measures that protect against or detect when the product has been tampered with.
Phases : Testing
The testing phase of the lifecycle should establish a method for determining whether the protection mechanism is sufficient to prevent unauthorized access.
Phases : Manufacturing
Ensure that all protection mechanisms are fully activated at the time of manufacturing and distribution.
Vulnerability Mapping Notes
Justification : This CWE entry is a Class and might have Base-level children that would be more appropriate
Comment : Examine children of this entry to see if there is a better fit
Related Attack Patterns
CAPEC-ID |
Attack Pattern Name |
CAPEC-401 |
Physically Hacking Hardware An adversary exploits a weakness in access control to gain access to currently installed hardware and precedes to implement changes or secretly replace a hardware component which undermines the system's integrity for the purpose of carrying out an attack. |
NotesNotes
This entry is still under development and will continue to see updates and content improvements.
Submission
Name |
Organization |
Date |
Date release |
Version |
CWE Content Team |
MITRE |
2020-05-28 +00:00 |
2020-02-24 +00:00 |
4.1 |
Modifications
Name |
Organization |
Date |
Comment |
CWE Content Team |
MITRE |
2020-08-20 +00:00 |
updated Common_Consequences, Description, Modes_of_Introduction, Name, Potential_Mitigations, Related_Attack_Patterns, Relationships |
CWE Content Team |
MITRE |
2020-12-10 +00:00 |
updated Potential_Mitigations |
CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Description |
CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes, Relationships |