CVE-2023-22742: RUSTSEC-2023-0003 - git2 does not verify SSH keys by default

CVE-2023-22742 · Severity: low · CVSS 3.1 · Published 2023-01-20

git2 does not verify SSH keys by default

Technologies: git2 (crates.io), libgit2-sys (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2023-22742 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-22742 being exploited in the wild.
How severe is CVE-2023-22742?
Low severity, with a CVSS score of 3.1, published 20 January 2023.
Which products and versions are affected?
git2 (crates.io) SEMVER:introduced=0,fixed=0.16.1; libgit2-sys (crates.io) SEMVER:introduced=0.0.0-0,fixed=0.13.5,introduced=0.14.0,fixed=0.14.2, SEMVER:introduced=0.14.0,fixed=0.14.2.
Is there a fix for CVE-2023-22742?
Yes. git2 (crates.io): upgrade to 0.16.1 or later; libgit2-sys (crates.io): upgrade to 0.14.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-22742?
Check whether you run git2 (crates.io) or libgit2-sys (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

  • git2 (crates.io): upgrade to 0.16.1 or later
    cargo update -p git2
  • libgit2-sys (crates.io): upgrade to 0.14.2 or later
    cargo update -p libgit2-sys

Affected products

  • git2 (crates.io) SEMVER:introduced=0,fixed=0.16.1
  • libgit2-sys (crates.io) SEMVER:introduced=0.0.0-0,fixed=0.13.5,introduced=0.14.0,fixed=0.14.2, SEMVER:introduced=0.14.0,fixed=0.14.2

Identifiers

  • CVE-2023-22742
  • GHSA-m4ch-rfv5-x5g3
  • RUSTSEC-2023-0003

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