Sensitive-data decryption via legacy TLS protocols
Published Apr 28, 2023 · Updated Jan 30, 2025
Weak cryptography in affected IBM Safer Payments releases allows remote attackers to decrypt sensitive information over the network. The server enables TLS 1.0 and TLS 1.1 by default, allowing connections to negotiate legacy protocols whose cryptography provides weaker protection. Network access to a TLS service is required; the reported consequence is disclosure of protected information, without integrity or availability impact.
Summary
What happened
Weak cryptography in affected IBM Safer Payments releases allows remote attackers to decrypt sensitive information over the network. The server enables TLS 1.0 and TLS 1.1 by default, allowing connections to negotiate legacy protocols whose cryptography provides weaker protection. Network access to a TLS service is required; the reported consequence is disclosure of protected information, without integrity or availability impact.
The record
- CVE
- CVE-2023-27557
- Published
- Apr 28, 2023
- Updated
- Jan 30, 2025
- Vendor
- IBM
- Product
- IBM Safer Payments
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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.1.0.00 <=6.1.1.02
- Affected versionversion=6.2.0.00 <=6.2.2.02
- Affected versionversion=6.3.0.00 <=6.3.1.02
- Affected versionversion=6.4.0.00 <=6.4.2.01
- Affected versionversion=6.5.0.00
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