Cleartext disclosure via trailing-dot HSTS bypass
Published Jun 1, 2022 · Updated Aug 3, 2024
Cleartext transmission in curl 7.82.0 through 7.83.0 allows context-dependent attackers to read HTTP traffic after an HSTS bypass. The HSTS code in lib/hsts.c compares cache entries and URL hostnames without consistently removing a trailing dot, so equivalent hostnames can miss the HTTPS upgrade. Exploitation requires HSTS use, a trailing-dot mismatch between the cached and requested hostname, and access to observe the resulting cleartext connection.
Summary
What happened
Cleartext transmission in curl 7.82.0 through 7.83.0 allows context-dependent attackers to read HTTP traffic after an HSTS bypass. The HSTS code in lib/hsts.c compares cache entries and URL hostnames without consistently removing a trailing dot, so equivalent hostnames can miss the HTTPS upgrade. Exploitation requires HSTS use, a trailing-dot mismatch between the cached and requested hostname, and access to observe the resulting cleartext connection.
The record
- CVE
- CVE-2022-30115
- Published
- Jun 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-319, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Fixed in 7.83.1
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
- HackerOne report 1557449proof 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