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

CVE-2023-38497 · Severity: low · CVSS 3.1 · Published 2023-08-03

Cargo not respecting umask when extracting crate archives

Technologies: cargo (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2023-38497 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-38497 being exploited in the wild.
How severe is CVE-2023-38497?
Low severity, with a CVSS score of 3.1, published 3 August 2023.
Which products and versions are affected?
cargo (crates.io) SEMVER:introduced=0,fixed=0.72.2.
Is there a fix for CVE-2023-38497?
Yes. cargo (crates.io): upgrade to 0.72.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-38497?
Check whether you run cargo (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • cargo (crates.io): upgrade to 0.72.2 or later
    cargo update -p cargo

Affected products

  • cargo (crates.io) SEMVER:introduced=0,fixed=0.72.2

Identifiers

  • CVE-2023-38497
  • GHSA-j3xp-wfr4-hx87

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.