Adjacent information disclosure via ignored TLS configuration
Published Mar 1, 2024 · Updated Apr 22, 2025
Weak outbound TLS handling in IBM WebSphere Application Server Liberty 17.0.0.3 through 24.0.0.2 allows adjacent attackers to read protected data. Outbound TLS handling fails to apply an unspecified user configuration, leaving connections protected less strongly than configured. Exploitation requires an adjacent network position; IBM reports no integrity or availability impact, and the affected setting is undisclosed.
Summary
What happened
Weak outbound TLS handling in IBM WebSphere Application Server Liberty 17.0.0.3 through 24.0.0.2 allows adjacent attackers to read protected data. Outbound TLS handling fails to apply an unspecified user configuration, leaving connections protected less strongly than configured. Exploitation requires an adjacent network position; IBM reports no integrity or availability impact, and the affected setting is undisclosed.
The record
- CVE
- CVE-2023-50312
- Published
- Mar 1, 2024
- Updated
- Apr 22, 2025
- Vendor
- IBM
- Product
- IBM WebSphere Application Server Liberty
- Classifications
- CWE-327, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2024CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=17.0.0.3 <=24.0.0.2
What conditions does exploitation require?
What is affected?
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