CWE-1316 · Słabość
Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges
- Abstrakcja
- Bazowa
- Status
- Szkic
- Dodano
- 1 czerwca 2020
- Ostatnia zmiana
- 11 grudnia 2025
Opis
The address map of the on-chip fabric has protected and unprotected regions overlapping, allowing an attacker to bypass access control to the overlapping portion of the protected region.
Various ranges can be defined in the system-address map, either in the memory or in Memory-Mapped-IO (MMIO) space. These ranges are usually defined using special range registers that contain information, such as base address and size. Address decoding is the process of determining for which range the incoming transaction is destined. To ensure isolation, ranges containing secret data are access-control protected.
Occasionally, these ranges could overlap. The overlap could either be intentional (e.g. due to a limited number of range registers or limited choice in choosing size of the range) or unintentional (e.g. introduced by errors). Some hardware designs allow dynamic remapping of address ranges assigned to peripheral MMIO ranges. In such designs, intentional address overlaps can be created through misconfiguration by malicious software. When protected and unprotected ranges overlap, an attacker could send a transaction and potentially compromise the protections in place, violating the principle of least privilege.
Skutki
Confidentiality, Integrity, Access Control, Authorization
Bypass Protection Mechanism; Read Memory; Modify Memory
Zapobieganie
Architecture and Design
When architecting the address map of the chip, ensure that protected and unprotected ranges are isolated and do not overlap. When designing, ensure that ranges hardcoded in Register-Transfer Level (RTL) do not overlap.
Implementation
Ranges configured by firmware should not overlap. If overlaps are mandatory because of constraints such as a limited number of registers, then ensure that no assets are present in the overlapped portion.
Testing
Validate mitigation actions with robust testing.
Przykłady podatności
- CVE-2009-4419 Attacker can modify MCHBAR register to overlap with an attacker-controlled region, which modification prevents the SENTER instruction from properly applying VT-d protection while a Measured Launch Environment is being launched.
Słabość nadrzędna
Kiedy powstaje
- Architecture and Design
- Implementation
Dotyczy
Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Bus/Interface Hardware, Not Technology-Specific
Uwagi
As of CWE 4.6, CWE-1260 and CWE-1316 are siblings under view 1000, but CWE-1260 might be a parent of CWE-1316. More analysis is warranted.
Źródła
- BARing the System - New vulnerabilities in Coreboot & UEFI-based Systems — Yuriy Bulygin, Oleksandr Bazhaniuk, Andrew Furtak, John Loucaides, Mikhail Gorobets, 2017
Wpis z katalogu CWE 4.20.