Các cách xuất hiện
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.
Nền tảng áp dụng
Ngôn ngữ
Lớp: Not Language-Specific (Undetermined)
Hệ điều hành
Lớp: Not OS-Specific (Undetermined)
Kiến trúc
Lớp: Not Architecture-Specific (Undetermined)
Công nghệ
Lớp: Not Technology-Specific (Undetermined)
Hậu quả phổ biến
| Phạm vi |
Tác động |
Khả năng xảy ra |
Confidentiality Integrity Access Control | Varies by Context
Ghi chú:
Sections of a product intended to have restricted access may be inadvertently or intentionally rendered accessible when the implemented physical protections are insufficient.
| |
Các biện pháp giảm thiểu tiềm năng
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.
Ghi chú ánh xạ lỗ hổng
Lý do : This CWE entry is a Class and might have Base-level children that would be more appropriate
Bình luận : Examine children of this entry to see if there is a better fit
Mẫu tấn công liên quan
| ID CAPEC |
Tên mẫu tấn công |
| 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. |
Ghi chú
This entry is still under development and will continue to see updates and content improvements.
Gửi
| Tên |
Tổ chức |
Ngày |
Ngày phát hành |
Version |
| CWE Content Team |
MITRE |
2020-05-28 +00:00 |
2020-02-24 +00:00 |
4.1 |
Sửa đổi
| Tên |
Tổ chức |
Ngày |
Bình luận |
| 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 |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Common_Consequences, Description |