First published: Wed Feb 08 2023(Updated: )
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 (c.f., <a href="https://access.redhat.com/security/cve/CVE-2022-39253">CVE-2022-39253</a>), the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as <a href="https://access.redhat.com/security/cve/CVE-2022-39253">CVE-2022-39253</a>.
Affected Software | Affected Version | How to fix |
---|---|---|
Git |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2168160 is categorized as moderate.
To fix REDHAT-BUG-2168160, update Git to the latest version provided by your distribution.
The risks associated with REDHAT-BUG-2168160 include unauthorized access to repositories due to improper handling of symbolic links.
Currently, REDHAT-BUG-2168160 affects multiple versions of Git prior to the patch release.
Yes, applying the latest security updates provided by your Linux distribution will mitigate this vulnerability.