Sensitive-information decryption via weak TLS and randomness
Published Mar 3, 2021 · Updated Sep 16, 2024
Weak cryptography in IBM Security Verify Bridge before 1.0.5 allows remote attackers to decrypt highly sensitive information. With no configured TLS preference, the bridge defaults to TLS 1.0, while LDAP bind authentication generates random values with an older, less secure randomizer. The exposure requires network access and conditions sufficient to defeat the weak protection; the reported consequence is disclosure, not data alteration or service interruption.
Summary
What happened
Weak cryptography in IBM Security Verify Bridge before 1.0.5 allows remote attackers to decrypt highly sensitive information. With no configured TLS preference, the bridge defaults to TLS 1.0, while LDAP bind authentication generates random values with an older, less secure randomizer. The exposure requires network access and conditions sufficient to defeat the weak protection; the reported consequence is disclosure, not data alteration or service interruption.
The record
- CVE
- CVE-2021-20441
- Published
- Mar 3, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Verify Bridge
- Classifications
- T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 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=unspecified
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