Sensitive-data decryption via weak cryptographic algorithms
Published Dec 6, 2022 · Updated Apr 23, 2025
Weak cryptography in IBM Sterling Secure Proxy 6.0.3 allows remote attackers to decrypt highly sensitive information over the network. IBM identifies exposure of weak TLS ciphers but has not published the specific cipher suites, component, or selection logic involved. Exploitation requires network access and a difficult cryptanalytic condition, and the reported consequence is disclosure of protected data without modification or service interruption.
Summary
What happened
Weak cryptography in IBM Sterling Secure Proxy 6.0.3 allows remote attackers to decrypt highly sensitive information over the network. IBM identifies exposure of weak TLS ciphers but has not published the specific cipher suites, component, or selection logic involved. Exploitation requires network access and a difficult cryptanalytic condition, and the reported consequence is disclosure of protected data without modification or service interruption.
The record
- CVE
- CVE-2022-34361
- Published
- Dec 6, 2022
- Updated
- Apr 23, 2025
- Vendor
- IBM
- Product
- IBM Sterling Secure Proxy
- Classifications
- CWE-327, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=6.0.3
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