CVE-2022-36113
published 2022-09-14CVE-2022-36113: Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk…
PriorityP345high8.1CVSS 3.1
AVNACLPRNUIRSUCNIHAH
EPSS
1.04%
60.6th percentile
Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes "ok" to the .cargo-ok file at the root of the extracted source code once it extracted all the files. It was discovered that Cargo allowed packages to contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempted to write "ok" into .cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok. This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. Note that by design Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the same attacks with build scripts and procedural macros. The vulnerability is present in all versions of Cargo. Rust 1.64, to be released on September 22nd, will include a fix for it. Since the vulnerability is just a more limited way to accomplish what a malicious build scripts or procedural macros can do, we decided not to publish Rust point releases backporting the security fix. Patch files are available for Rust 1.63.0 are available in the wg-security-response repository for people building their own toolchain.
Mitigations We recommend users of alternate registries to exercise care in which package they download, by only including trusted dependencies in their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be able to cause damage regardless of these vulnerabilities. cra
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | cargo | < cargo 0.63.1-1 (bookworm) | cargo 0.63.1-1 (bookworm) |
| debian | rust-cargo | < cargo 0.63.1-1 (bookworm) | cargo 0.63.1-1 (bookworm) |
| msrc | azl3_rust_1.75.0-14_on_azure_linux_3.0 | — | — |
| msrc | azl3_rust_1.86.0-1_on_azure_linux_3.0 | — | — |
| rust-lang | cargo | < 0.65.0 | 0.65.0 |
| rust-lang | cargo | — | — |
| rust-lang | cargo | >= 0 < 0.63.1-1 | 0.63.1-1 |
| rust-lang | cargo | >= 0 < 0.65.0 | 0.65.0 |
| rust-lang | cargo | >= 0.66.0 < 0.67.0 | 0.67.0 |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
osv8.1HIGH
vendor_debian4.6MEDIUM
vendor_msrc4.6MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Microsoft
Extracting malicious crates can corrupt arbitrary files
vendor_msrc·2022-09-13·CVSS 4.6
CVE-2022-36113 [MEDIUM] CWE-22 Extracting malicious crates can corrupt arbitrary files
Extracting malicious crates can corrupt arbitrary files
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
GitHub_M: GitHub_M
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https:/
Debian
CVE-2022-36113: cargo - Cargo is a package manager for the rust programming language. After a package is...
vendor_debian·2022·CVSS 4.6
CVE-2022-36113 [MEDIUM] CVE-2022-36113: cargo - Cargo is a package manager for the rust programming language. After a package is...
Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes "ok" to the .cargo-ok file at the root of the extracted source code once it extracted all the files. It was discovered that Cargo allowed packages to contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempted to write "ok" into .cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok. This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. Note that by design Cargo allows code execution at build time, due to build
OSV
Cargo extracting malicious crates can corrupt arbitrary files
osv·2022-09-16
CVE-2022-36113 [LOW] Cargo extracting malicious crates can corrupt arbitrary files
Cargo extracting malicious crates can corrupt arbitrary files
The Rust Security Response WG was notified that Cargo did not prevent extracting some malformed packages downloaded from alternate registries. An attacker able to upload packages to an alternate registry could corrupt arbitary files when Cargo downloaded the package.
The severity of this vulnerability is "low" for users of alternate registries. Users relying on crates.io are not affected.
Note that **by design** Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the s
GHSA
Cargo extracting malicious crates can corrupt arbitrary files
ghsa·2022-09-16
CVE-2022-36113 [LOW] CWE-22 Cargo extracting malicious crates can corrupt arbitrary files
Cargo extracting malicious crates can corrupt arbitrary files
The Rust Security Response WG was notified that Cargo did not prevent extracting some malformed packages downloaded from alternate registries. An attacker able to upload packages to an alternate registry could corrupt arbitary files when Cargo downloaded the package.
The severity of this vulnerability is "low" for users of alternate registries. Users relying on crates.io are not affected.
Note that **by design** Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the s
OSV
CVE-2022-36113: Cargo is a package manager for the rust programming language
osv·2022-09-14·CVSS 8.1
CVE-2022-36113 [HIGH] CVE-2022-36113: Cargo is a package manager for the rust programming language
Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes "ok" to the .cargo-ok file at the root of the extracted source code once it extracted all the files. It was discovered that Cargo allowed packages to contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempted to write "ok" into .cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok. This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. Note that by design Cargo allows code execution at build time, due to build
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/rust-lang/cargo/commit/97b80919e404b0768ea31ae329c3b4da54bed05ahttps://github.com/rust-lang/cargo/security/advisories/GHSA-rfj2-q3h3-hm5jhttps://github.com/rust-lang/cargo/commit/97b80919e404b0768ea31ae329c3b4da54bed05ahttps://github.com/rust-lang/cargo/security/advisories/GHSA-rfj2-q3h3-hm5j
2022-09-14
Published