Skip to main content
Public proof of conceptFix available

CVE-2023-38497

A public proof of concept exists; no exploitation attested.

  • Published2023-08-04
  • WeaknessCWE-278 · CWE-732

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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`.

Timeline

dates in UTC
  1. 2023-08-0416:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-38497?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-38497?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP · OSV
Fedoraproject fedora
BranchAffectedFixed in
38.x= 38no fix published
Rust-lang cargo
BranchAffectedFixed in
0.72< 0.72.20.72.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rustAlmaLinux:9all versions · fixed in 1.66.1-2.el9_2and 14 other packages
  • rustAlmaLinux:8all versions · fixed in 1.66.1-2.module_el8.8.0+3604+b9bee1fcand 14 other packages

Full record on NVD

Fix

Advisories and patches

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedlucas-cauhe/cargo-perm
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-10-08
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.9read 2026-10-23
  • NVDCVSS 3.17.3read 2026-10-23
  • CNAweakness (CWE)CWE-278read 2026-10-23
  • NVDweakness (CWE)CWE-732read 2026-10-23
  • FIRST EPSSEPSS score0.7 %2026-10-23
  • PoC-in-GitHubproof of concept1read 2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Published
2023-08-04
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2023-38497?

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`.

Is CVE-2023-38497 actively exploited?

Active exploitation of CVE-2023-38497 has not been confirmed. Its EPSS score was 0.7% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-38497?

CVE-2023-38497 has a CVSS v3 base score of 7.3 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

Running cargo? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month