Disk exhaustion via unlimited crate extraction
Published Sep 14, 2022 · Updated Apr 23, 2025
Uncontrolled resource consumption in Cargo before 0.65.0 and 0.66.0 allows remote authenticated users to exhaust disk via a crafted crate. The registry extraction path passes gzip-decoded crate data to the tar unpacker without limiting expanded bytes, so a small archive can expand until the file system fills. Exploitation requires control of a package on an alternate registry and a Cargo user to download it; crates.io rejects such packages.
Summary
What happened
Uncontrolled resource consumption in Cargo before 0.65.0 and 0.66.0 allows remote authenticated users to exhaust disk via a crafted crate. The registry extraction path passes gzip-decoded crate data to the tar unpacker without limiting expanded bytes, so a small archive can expand until the file system fills. Exploitation requires control of a package on an alternate registry and a Cargo user to download it; crates.io rejects such packages.
The record
- CVE
- CVE-2022-36114
- Published
- Sep 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- Rust Project
- Product
- Cargo
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=< 0.65.0
- Affected versionversion== 0.66.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
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