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 Software | Affected Version | How 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 |
- 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.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Git vulnerability is CVE-2023-22490.
The severity level of CVE-2023-22490 is medium.
Git can be tricked into using its local clone optimization even when using a non-local transport by using a specially-crafted repository.
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.
To fix CVE-2023-22490, update Git to version 2.39.3-1.el8_8 or 2.39.3-1.el9_2.