Sensitive-data decryption via weak cryptography
Published Apr 19, 2022 · Updated Sep 17, 2024
Cryptographic weakness in IBM Security Guardium 10.5 and 11.3 allows remote attackers to decrypt sensitive information over network connections. Guardium enables weaker-than-expected TLS algorithms, allowing a network attacker able to negotiate the affected service to recover protected data; exploitation requires no account but a favorable high-complexity negotiation.
Summary
What happened
Cryptographic weakness in IBM Security Guardium 10.5 and 11.3 allows remote attackers to decrypt sensitive information over network connections. Guardium enables weaker-than-expected TLS algorithms, allowing a network attacker able to negotiate the affected service to recover protected data; exploitation requires no account but a favorable high-complexity negotiation.
The record
- CVE
- CVE-2021-39076
- Published
- Apr 19, 2022
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM Security Guardium
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=10.5
- Affected versionversion=11.3
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