Sensitive-data decryption via weak cryptographic algorithms
Published Aug 30, 2021 · Updated Sep 16, 2024
Cryptographic weakness in IBM Sterling Secure Proxy 2.4.3.2, 3.4.3.2, 6.0.1, and 6.0.2 allows remote attackers to decrypt sensitive information. IBM has not published the affected cryptographic algorithm, protocol, code locus, or operation that applies it to untrusted data. Exploitation requires unauthenticated network access and high attack complexity; the reported consequence is disclosure, not alteration or interruption.
Summary
What happened
Cryptographic weakness in IBM Sterling Secure Proxy 2.4.3.2, 3.4.3.2, 6.0.1, and 6.0.2 allows remote attackers to decrypt sensitive information. IBM has not published the affected cryptographic algorithm, protocol, code locus, or operation that applies it to untrusted data. Exploitation requires unauthenticated network access and high attack complexity; the reported consequence is disclosure, not alteration or interruption.
The record
- CVE
- CVE-2021-29723
- Published
- Aug 30, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 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=2.4.3.2
- Affected versionversion=3.4.3.2
- Affected versionversion=6.0.1
- Affected versionversion=6.0.2
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