Unintended file deletion via stale output filename
Published Jun 1, 2022 · Updated Aug 3, 2024
Incorrect name resolution in the curl command-line tool 7.83.0 allows attackers to delete an unintended local file via a failed transfer. In post_per_transfer, the error cleanup unlinks per->outfile, the original requested name, instead of outs->filename, the numbered name selected by --no-clobber. The user must combine --no-clobber with --remove-on-error, encounter an existing destination, and experience a transfer error; deletion is limited to the original output path.
Summary
What happened
Incorrect name resolution in the curl command-line tool 7.83.0 allows attackers to delete an unintended local file via a failed transfer. In post_per_transfer, the error cleanup unlinks per->outfile, the original requested name, instead of outs->filename, the numbered name selected by --no-clobber. The user must combine --no-clobber with --remove-on-error, encounter an existing destination, and experience a transfer error; deletion is limited to the original output path.
The record
- CVE
- CVE-2022-27778
- Published
- Jun 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-706, T1070.004
- 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
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