Protected-data compromise via improper signature verification
Published Jul 11, 2022 · Updated Sep 16, 2024
Improper signature verification in Dell BSAFE Crypto-C Micro Edition before 4.1.5 allows remote attackers to compromise protected data. The library improperly verifies cryptographic signatures, but Dell does not disclose the affected API, accepted malformed input, or failed validation step. No authentication or user action is required, but exploitation depends on a hosting application exposing the library to attacker-controlled cryptographic input.
Summary
What happened
Improper signature verification in Dell BSAFE Crypto-C Micro Edition before 4.1.5 allows remote attackers to compromise protected data. The library improperly verifies cryptographic signatures, but Dell does not disclose the affected API, accepted malformed input, or failed validation step. No authentication or user action is required, but exploitation depends on a hosting application exposing the library to attacker-controlled cryptographic input.
The record
- CVE
- CVE-2020-35169
- Published
- Jul 11, 2022
- Updated
- Sep 16, 2024
- Vendor
- Dell
- Product
- BSAFE Crypto-C Micro Edition
- Classifications
- CWE-347, CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <4.1.5 and 4.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo