Application crash via unterminated .netrc line
Published Dec 5, 2022 · Updated Nov 19, 2024
Stack-based buffer overflow in curl 7.84.0 through 7.85.0 allows context-dependent attackers to crash an application via a crafted .netrc file. The parsenetrc routine reads into a 4096-byte stack buffer with fgets, then advances past a full unterminated line and writes a zero byte beyond the buffer. The attacker must supply or influence a .netrc file that the application directs curl to parse; the documented consequence is a process crash.
Summary
What happened
Stack-based buffer overflow in curl 7.84.0 through 7.85.0 allows context-dependent attackers to crash an application via a crafted .netrc file. The parsenetrc routine reads into a 4096-byte stack buffer with fgets, then advances past a full unterminated line and writes a zero byte beyond the buffer. The attacker must supply or influence a .netrc file that the application directs curl to parse; the documented consequence is a process crash.
The record
- CVE
- CVE-2022-35260
- Published
- Dec 5, 2022
- Updated
- Nov 19, 2024
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-121, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2022CVE publishedPublication date reported by the CVE source.
- Nov 19, 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.86.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.
Public exploit references
- HackerOne report 1721098proof 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