CWEweakness
CWE-1323 Improper Management of Sensitive Trace Data
- Abstraction
- Base
- Structure
- Simple
- Status
- Draft
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
Trace data collected from several sources on the
System-on-Chip (SoC) is stored in unprotected locations or
transported to untrusted agents.
Common consequences
• Confidentiality: Read Memory — An adversary can read secret values if they are captured in debug traces and stored unsafely. If trace data (such as from debug) is stored in unprotected memory, an
untrusted software debugger can access these traces and
extract secret information. Additionally, if
security-sensitive traces are not tagged as secure, an
untrusted hardware debugger might access them to extract
confidential information.
Potential mitigations
• [Implementation] Since
these traces are collected from several security-sensitive
sources, they must be protected against untrusted
debuggers.
Tag traces to indicate owner and debugging privilege level (designer, OEM, or end user) needed to access that trace.
Related
Attack pattern · CAPEC (3)
Child of · CWE (1)
- CWE-284 Improper Access Control weakness
Referenced by CAPEC · weakness (3)
Referenced by CVE · weakness (2)
- CVE-2024-54173 IBM MQ 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD reveals potentially sensitive information in trace files that could be read by a local user… vulnerability
- CVE-2024-49338 IBM App Connect Enterprise 12.0.1.0 through 12.0.7.0and 13.0.1.0 under certain configurations could allow a privileged user to obtain JMS… vulnerability