Exposure of Sensitive System Information Due to Uncleared Debug Information

Opis

The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.

Security sensitive values, keys, intermediate steps of cryptographic operations, etc. are stored in temporary registers in the hardware. If these values are not cleared when debug mode is entered they may be accessed by a debugger allowing sensitive information to be accessible by untrusted parties.

Skutki

• Confidentiality

  Read Memory

• Access Control

  Bypass Protection Mechanism

Zapobieganie

• Architecture and Design

  Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.

Przykłady podatności

• CVE-2021-33080 Uncleared debug information in memory accelerator for SSD product exposes sensitive system information
• CVE-2022-31162 Rust library leaks Oauth client details in application debug logs

Słabość nadrzędna

• CWE-212 Improper Removal of Sensitive Information Before Storage or Transfer

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific

Źródła

1. Bad Code aes1_wrapper.sv — 2021
2. Good Code aes1_wrapper.sv — 2021