Sensitive-data decryption via weak cryptographic algorithms
Published Jun 4, 2020 · Updated Sep 16, 2024
Weak cryptography in IBM Security Guardium 10.5 through 11.1 allows local users with high privileges to decrypt highly sensitive information. IBM identifies weaker-than-expected cryptographic algorithms but does not disclose the affected component, algorithm, key handling, or cryptographic operation. Exploitation requires local access, high privileges, and high complexity; the documented consequence is disclosure of protected information without data alteration or service interruption.
Summary
What happened
Weak cryptography in IBM Security Guardium 10.5 through 11.1 allows local users with high privileges to decrypt highly sensitive information. IBM identifies weaker-than-expected cryptographic algorithms but does not disclose the affected component, algorithm, key handling, or cryptographic operation. Exploitation requires local access, high privileges, and high complexity; the documented consequence is disclosure of protected information without data alteration or service interruption.
The record
- CVE
- CVE-2020-4191
- Published
- Jun 4, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Guardium
- Classifications
- CWE-327
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 4, 2020CVE 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=11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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