Heap disclosure via freed SSH fingerprint
Published May 26, 2023 · Updated Jan 15, 2025
Use-after-free in libcurl 7.81.0 through 8.0.1 allows remote attackers to expose heap data in failed SSH key-check errors. The ssh_check_fingerprint function frees fingerprint_b64 before failf formats that pointer into a mismatch error, exposing up to 186 heap bytes. The flaw requires a libssh2 build, CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256, a mismatching server key, and either verbose output or an error buffer.
Summary
What happened
Use-after-free in libcurl 7.81.0 through 8.0.1 allows remote attackers to expose heap data in failed SSH key-check errors. The ssh_check_fingerprint function frees fingerprint_b64 before failf formats that pointer into a mismatch error, exposing up to 186 heap bytes. The flaw requires a libssh2 build, CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256, a mismatching server key, and either verbose output or an error buffer.
The record
- CVE
- CVE-2023-28319
- Published
- May 26, 2023
- Updated
- Jan 15, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Jan 15, 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=Fixed in 8.1.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
- HackerOne report 1913733proof of concept · unverified
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