CWE
59 402
Advisory Published
CVE Published
CVE Published
Updated

CVE-2023-22490: Git vulnerable to local clone-based data exfiltration with non-local transports

First published: Wed Feb 08 2023(Updated: )

A vulnerability was found in Git. Using a specially-crafted repository, Git can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links (CVE-2022-39253), the objects directory may still be a symbolic link.

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
redhat/git<0:2.39.3-1.el8_8
0:2.39.3-1.el8_8
redhat/git<0:2.39.3-1.el9_2
0:2.39.3-1.el9_2
Git Git-shell<2.30.8
Git Git-shell>=2.31.0<2.31.7
Git Git-shell>=2.32.0<2.32.6
Git Git-shell>=2.33.0<2.33.7
Git Git-shell>=2.34.0<2.34.7
Git Git-shell>=2.35.0<2.35.7
Git Git-shell>=2.36.0<2.36.5
Git Git-shell>=2.37.0<2.37.6
Git Git-shell>=2.38.0<2.38.4
Git Git-shell>=2.39.0<2.39.2

Remedy

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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this Git vulnerability?

    The vulnerability ID for this Git vulnerability is CVE-2023-22490.

  • What is the severity level of CVE-2023-22490?

    The severity level of CVE-2023-22490 is medium.

  • How can Git be tricked into using its local clone optimization even when using a non-local transport?

    Git can be tricked into using its local clone optimization even when using a non-local transport by using a specially-crafted repository.

  • What versions of Git are affected by this vulnerability?

    Versions of Git prior to 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 are affected by this vulnerability.

  • How can I fix CVE-2023-22490?

    To fix CVE-2023-22490, update Git to version 2.39.3-1.el8_8 or 2.39.3-1.el9_2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203