Sensitive-data decryption via weak cryptographic algorithms
Published Jan 7, 2022 · Updated Sep 16, 2024
Weak cryptography in IBM Security Verify Access 10.0.0, 10.0.1.0, and 10.0.2.0 allows remote attackers to decrypt sensitive data. IBM has not disclosed the affected cryptographic component, algorithm, or protocol, so the precise operation on untrusted traffic remains unknown. Exploitation requires network access and high complexity but no authentication or user interaction, and the reported consequence is disclosure only.
Summary
What happened
Weak cryptography in IBM Security Verify Access 10.0.0, 10.0.1.0, and 10.0.2.0 allows remote attackers to decrypt sensitive data. IBM has not disclosed the affected cryptographic component, algorithm, or protocol, so the precise operation on untrusted traffic remains unknown. Exploitation requires network access and high complexity but no authentication or user interaction, and the reported consequence is disclosure only.
The record
- CVE
- CVE-2021-38921
- Published
- Jan 7, 2022
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Verify Access
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 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=10.0.0
- Affected versionversion=10.0.1.0
- Affected versionversion=10.0.2.0
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