CVE-2023-384977.8HighCWE-278

CVE-2023-38497: Cargo not respecting umask when extracting crate archives

rust-lang · cargo

Affected: rust-lang cargo · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.7%probability of exploitation in the next 30 days

53rd percentile

050100

Higher than 53% of scored CVEs

7.8HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one's system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

rust-lang · cargo< 0.72.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Insecure Preserved Inherited Permissions · Access Control
Vendor: rust-lang
Published: August 2023
Band: Unlikely (under 1%), August 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2023-38497 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.