Achtergrondinformatie
Introductiemodi
Architecture and Design
Implementation
Toepasselijke platforms
Taal
Klasse: Not Language-Specific (Undetermined)
Besturingssystemen
Klasse: Not OS-Specific (Undetermined)
Architecturen
Klasse: Not Architecture-Specific (Undetermined)
Technologieën
Naam: Memory Hardware (Undetermined)
Naam: Processor Hardware (Undetermined)
Naam: Microcontroller Hardware (Undetermined)
Naam: Network on Chip Hardware (Undetermined)
Klasse: System on Chip (Undetermined)
Veelvoorkomende gevolgen
| Bereik |
Impact |
Waarschijnlijkheid |
| Confidentiality | Read Memory
Opmerking:
An untrusted agent might be blocked from accessing a memory region, but it is not blocked from accessing the corresponding aliased memory region.
| High |
| Integrity | Modify Memory
Opmerking:
An untrusted agent might be blocked from accessing a memory region, but it is not blocked from accessing the corresponding aliased memory region.
| High |
| Availability | DoS: Instability | High |
Mogelijke risicobeperkingen
Phases : Architecture and Design // Implementation
The checks should be applied for consistency access rights between primary memory regions and any mirrored or aliased memory regions. If different memory protection units (MPU) are protecting the aliased regions, their protected range definitions and policies should be synchronized.
Phases : Architecture and Design // Implementation
The controls that allow enabling memory aliases or changing the size of mapped memory regions should only be programmable by trusted software components.
Notities kwetsbaarheidsmapping
Rechtvaardiging : 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.
Opmerking : 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.
Gerelateerde aanvalspatronen
| CAPEC ID |
Naam aanvalspatroon |
| CAPEC-456 |
Infected Memory
An adversary inserts malicious logic into memory enabling them to achieve a negative impact. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems that are still under development and part of the supply chain. |
| CAPEC-679 |
Exploitation of Improperly Configured or Implemented Memory Protections
|
Indiening
| Naam |
Organisatie |
Datum |
Releasedatum |
Version |
| Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna, Narasimha Kumar V Mangipudi |
Intel Corporation |
2020-04-29 +00:00 |
2020-02-24 +00:00 |
4.1 |
Wijzigingen
| Naam |
Organisatie |
Datum |
Opmerking |
| CWE Content Team |
MITRE |
2020-08-20 +00:00 |
updated Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2022-04-28 +00:00 |
updated Applicable_Platforms, Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2022-06-28 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated Demonstrative_Examples |
| 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, Demonstrative_Examples, Description |