RHSA-2023:3245HighCVSS 7.8

Red Hat Security Advisory: git security update

Published
May 22, 2023
Last Modified
November 6, 2026

🔗 CVE IDs covered (5)

📋 Description

CVE-2023-22490 — git: data exfiltration with maliciously crafted repository CVE-2023-23946 — git: git apply: a path outside the working tree can be overwritten with crafted input CVE-2023-25652 — git: by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents CVE-2023-25815 — git: malicious placement of crafted messages when git was compiled with runtime prefix CVE-2023-29007 — git: arbitrary configuration injection when renaming or deleting a section from a configuration file

🎯 Affected products52

  • Red Hat Enterprise Linux AppStream (v. 9)
  • git-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-0:2.39.3-1.el9_2.src as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-all-0:2.39.3-1.el9_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-debuginfo-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-debuginfo-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-debuginfo-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-debuginfo-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-core-doc-0:2.39.3-1.el9_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-debuginfo-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-debuginfo-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-debuginfo-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-credential-libsecret-debuginfo-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-0:2.39.3-1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-0:2.39.3-1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-debuginfo-0:2.39.3-1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • git-daemon-debuginfo-0:2.39.3-1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • +22 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: - Avoid cloning repositories from untrusted sources with --recurse-submodules. - Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs. Workaround: Use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

🔗 References (8)