Sensitive-data decryption via weak cryptographic algorithms
Published Jul 7, 2021 · Updated Sep 16, 2024
Weak cryptography in IBM Guardium Data Encryption 3.0.0.2 and 4.0.0.4 allows remote attackers to decrypt highly sensitive information. IBM identifies only weaker-than-expected cryptographic algorithms and does not disclose the affected component, algorithm, or incorrect operation. The unauthenticated attack requires unspecified high-complexity conditions and exposes protected data without modifying it or interrupting service.
Summary
What happened
Weak cryptography in IBM Guardium Data Encryption 3.0.0.2 and 4.0.0.4 allows remote attackers to decrypt highly sensitive information. IBM identifies only weaker-than-expected cryptographic algorithms and does not disclose the affected component, algorithm, or incorrect operation. The unauthenticated attack requires unspecified high-complexity conditions and exposes protected data without modifying it or interrupting service.
The record
- CVE
- CVE-2021-20379
- Published
- Jul 7, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- Guardium Data Encryption
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2021CVE 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=3.0.0.2
- Affected versionversion=4.0.0.4
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