배경 세부 정보
취약점 도입 방식
Implementation : Keys, code, configuration settings, and other data should be programmed in write-once or read-only memory instead of writable memory.
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)
운영 체제
클래스: Not OS-Specific (Undetermined)
아키텍처
클래스: Not Architecture-Specific (Undetermined)
기술
클래스: Not Technology-Specific (Undetermined)
일반적인 결과
| 범위 |
영향 |
가능성 |
| Integrity | Varies by Context
참고: Security is lost if assets assumed to be immutable can be modified. | |
잠재적 완화 방법
Phases : Implementation
Storing immutable code or data in read-only memory
(ROM), fuses, or one-time programmable (OTP) memory
provides strong integrity guarantees and provides a
root of trust for securing the rest of the system.
취약점 매핑 메모
근거 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
댓글 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
관련 공격 패턴
| CAPEC ID |
공격 패턴 이름 |
| CAPEC-458 |
Flash Memory Attacks
An adversary inserts malicious logic into a product or technology via flashing the on-board memory with a code-base that contains malicious logic. Various attacks exist against the integrity of flash memory, the most direct being rootkits coded into the BIOS or chipset of a device. |
| CAPEC-679 |
Exploitation of Improperly Configured or Implemented Memory Protections
|
메모
This entry is still under development and will continue to
see updates and content improvements.
As of CWE 4.3, CWE-1282 and CWE-1233 are being investigated
for potential duplication or overlap.
제출
| 이름 |
조직 |
날짜 |
출시일 |
Version |
| Nicole Fern |
Cycuity (originally submitted as Tortuga Logic) |
2020-05-15 +00:00 |
2020-02-24 +00:00 |
4.1 |
수정 사항
| 이름 |
조직 |
날짜 |
댓글 |
| CWE Content Team |
MITRE |
2020-08-20 +00:00 |
updated Demonstrative_Examples, Description, Modes_of_Introduction, Name |
| CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Maintenance_Notes |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2022-04-28 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Potential_Mitigations |