Weakness (CWE)
CWE-1258: Exposure of Sensitive System Information Due to Uncleared Debug Information
The hardware product enters debug mode but does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations.
More detail
Security sensitive values, keys, intermediate steps of cryptographic operations, etc. are stored in temporary registers in the hardware.
How to prevent it (1 mitigation)
-
Architecture and Design
Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.
Source: MITRE CWE-1258
4 results · Clear filters · Feed
-
High 7.5
WordPress WPJAM Basic plugin <= 7.0.2.1 - Sensitive Data Exposure vulnerability
Subscriber Sensitive Data Exposure in WPJAM Basic <= 7.0.2.1 versions.
-
High 7.5
WordPress JetBlog plugin <= 2.4.8 - Sensitive Data Exposure vulnerability
Unauthenticated Sensitive Data Exposure in JetBlog <= 2.4.8 versions.
-
High 7.5
Exposure of sensitive Slack webhook URLs in debug logs and traces
Slack Morphism is a modern client library for Slack Web/Events API/Socket Mode and Block Kit. Debug logs expose sensitive URLs for Slack webhooks that contain private information. The problem is fixed in version 1.3.2 which redacts sensitive URLs for webhooks…
-
High 7.5
Slack Morphism for Rust before 0.41.0 can accidentally leak Slack OAuth client information in application debug logs
Slack Morphism is an async client library for Rust. Prior to 0.41.0, it was possible for Slack OAuth client information to leak in application debug logs. Stricter and more secure debug formatting was introduced in v0.41.0 for OAuth secret types to reduce the…