No. Junglewise Threat Intelligence has no report of CVE-2024-35197 being exploited in the wild.
How severe is CVE-2024-35197?
Low severity, with a CVSS score of 3.1, published 22 May 2024.
Which products and versions are affected?
gitoxide (crates.io) SEMVER:introduced=0,fixed=0.36.0; gitoxide-core (crates.io) SEMVER:introduced=0,fixed=0.38.0; gix (crates.io) SEMVER:introduced=0,fixed=0.63.0; gix-index (crates.io) SEMVER:introduced=0,fixed=0.33.0, SEMVER:introduced=0.0.0-0,fixed=0.33.0; and 3 more.
Is there a fix for CVE-2024-35197?
Yes. gitoxide (crates.io): upgrade to 0.36.0 or later; gitoxide-core (crates.io): upgrade to 0.38.0 or later; gix (crates.io): upgrade to 0.63.0 or later; gix-index (crates.io): upgrade to 0.33.0 or later; gix-ref (crates.io): upgrade to 0.44.0 or later; gix-worktree (crates.io): upgrade to 0.34.0 or later; gix-worktree-state (crates.io): upgrade to 0.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-35197?
Check whether you run gitoxide (crates.io), gitoxide-core (crates.io), gix (crates.io) or one of the others listed 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
gitoxide (crates.io): upgrade to 0.36.0 or later
cargo update -p gitoxide
gitoxide-core (crates.io): upgrade to 0.38.0 or later
cargo update -p gitoxide-core
gix (crates.io): upgrade to 0.63.0 or later
cargo update -p gix
gix-index (crates.io): upgrade to 0.33.0 or later
cargo update -p gix-index
gix-ref (crates.io): upgrade to 0.44.0 or later
cargo update -p gix-ref
gix-worktree (crates.io): upgrade to 0.34.0 or later
cargo update -p gix-worktree
gix-worktree-state (crates.io): upgrade to 0.11.0 or later