Credential disclosure via incomplete redirect-origin check
Published Jun 1, 2022 · Updated Nov 20, 2024
Credential exposure in curl 4.9 through 7.82.0 allows remote attackers to read authentication and cookie headers through HTTP redirects. Curl_http_output_auth and Curl_add_custom_headers compare only the original hostname on a followed redirect, ignoring a changed port or URL scheme. Exploitation requires a followed redirect while custom Authorization or Cookie headers are attached, exposing those credentials to a server reached on the alternate origin.
Summary
What happened
Credential exposure in curl 4.9 through 7.82.0 allows remote attackers to read authentication and cookie headers through HTTP redirects. Curl_http_output_auth and Curl_add_custom_headers compare only the original hostname on a followed redirect, ignoring a changed port or URL scheme. Exploitation requires a followed redirect while custom Authorization or Cookie headers are attached, exposing those credentials to a server reached on the alternate origin.
The record
- CVE
- CVE-2022-27776
- Published
- Jun 1, 2022
- Updated
- Nov 20, 2024
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-522, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2022CVE publishedPublication date reported by the CVE source.
- Nov 20, 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 curl 7.83.0
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