False TLS success via zero-valued error propagation
Published Oct 29, 2024 · Updated Oct 30, 2024
Improper SSL error handling in Asio before 1.13.0 allows remote attackers to have failed TLS operations reported as successful. The SSL engine constructs an error_code from a zero-valued system error after SSL_ERROR_SYSCALL, clearing the error instead of recording the failed operation. The condition requires an application built with the affected headers to use Asio SSL support, and downstream impact depends on the caller's handling of false success.
Summary
What happened
Improper SSL error handling in Asio before 1.13.0 allows remote attackers to have failed TLS operations reported as successful. The SSL engine constructs an error_code from a zero-valued system error after SSL_ERROR_SYSCALL, clearing the error instead of recording the failed operation. The condition requires an application built with the affected headers to use Asio SSL support, and downstream impact depends on the caller's handling of false success.
The record
- CVE
- CVE-2019-25219
- Published
- Oct 29, 2024
- Updated
- Oct 30, 2024
- Vendor
- Asio
- Product
- Asio
- Classifications
- CWE-1188
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 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=0 <1.13.0
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