Sensitive data decryption via weak cryptography
Published Aug 22, 2024 · Updated Mar 13, 2026
Weak cryptography in IBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 allows remote attackers to decrypt sensitive data. The product's bundled IBM Java SE cryptographic implementation uses weaker-than-expected algorithms, but IBM has not disclosed the algorithm, protocol, or code path that selects them. Exploitation is unauthenticated over a network, requires high attack complexity, and affects confidentiality without reported data modification or service interruption.
Summary
What happened
Weak cryptography in IBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 allows remote attackers to decrypt sensitive data. The product's bundled IBM Java SE cryptographic implementation uses weaker-than-expected algorithms, but IBM has not disclosed the algorithm, protocol, or code path that selects them. Exploitation is unauthenticated over a network, requires high attack complexity, and affects confidentiality without reported data modification or service interruption.
The record
- CVE
- CVE-2024-39745
- Published
- Aug 22, 2024
- Updated
- Mar 13, 2026
- Vendor
- IBM
- Product
- IBM Sterling Connect:Direct Web Services
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record 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, 6.1, 6.2, 6.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