CWE-1323
Improper Management of Sensitive Trace Data
Draft
2020-12-10
00h00 +00:00
00h00 +00:00
2025-12-11
00h00 +00:00
00h00 +00:00
Meldingen voor een CWE
Blijf op de hoogte van wijzigingen voor een specifieke CWE.
Naam: Improper Management of Sensitive Trace Data
Trace data collected from several sources on the
System-on-Chip (SoC) is stored in unprotected locations or
transported to untrusted agents.
Algemene informatie
Introductiemodi
Architecture and DesignImplementation
Toepasselijke platforms
Taal
Class: Not Language-Specific (Undetermined)Besturingssystemen
Class: Not OS-Specific (Undetermined)Architecturen
Class: Not Architecture-Specific (Undetermined)Technologieën
Class: System on Chip (Undetermined)Veelvoorkomende gevolgen
| Bereik | Impact | Waarschijnlijkheid |
|---|---|---|
| Confidentiality | Read Memory Note: An adversary can read secret values if they are captured in debug traces and stored unsafely. |
Mogelijke risicobeperkingen
Phases : ImplementationTag traces to indicate owner and debugging privilege level (designer, OEM, or end user) needed to access that trace.
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-150 | Collect Data from Common Resource Locations
An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks. |
| CAPEC-167 | White Box Reverse Engineering
An attacker discovers the structure, function, and composition of a type of computer software through white box analysis techniques. White box techniques involve methods which can be applied to a piece of software when an executable or some other compiled object can be directly subjected to analysis, revealing at least a portion of its machine instructions that can be observed upon execution. |
| CAPEC-545 | Pull Data from System Resources
An adversary who is authorized or has the ability to search known system resources, does so with the intention of gathering useful information. System resources include files, memory, and other aspects of the target system. In this pattern of attack, the adversary does not necessarily know what they are going to find when they start pulling data. This is different than CAPEC-150 where the adversary knows what they are looking for due to the common location. |
Referenties
REF-1150
Secure design-for-debug for Systems-on-ChipJerry Backer, David Hely, Ramesh Karri.
https://ieeexplore.ieee.org/document/7342418
REF-1151
Secure and Flexible Trace-Based Debugging of Systems-on-ChipJerry Backer, David Hely, Ramesh Karri.
https://dl.acm.org/doi/pdf/10.1145/2994601
Indiening
| Naam | Organisatie | Datum | Releasedatum | Version |
|---|---|---|---|---|
| Hareesh Khattri, Parbati K. Manna, and Arun Kanuparthi | Intel Corporation | 4.3 |
Wijzigingen
| Naam | Organisatie | Datum | Opmerking |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Weakness_Ordinalities |
