CVE-2022-39253
Git subject to exposure of sensitive information via local clone of symbolic links
In short
Git can expose sensitive files on your computer when you clone a malicious repository locally. An attacker can trick you into cloning a repo with a symbolic link that points to private data, and Git may copy or link that sensitive information into the cloned repository.
Technical detail
When Git performs local cloning with hardlinks or copying (CWE-200: Information Exposure), a malicious repository containing symbolic links in $GIT_DIR/objects can expose sensitive local files. The attack vector involves social engineering a user to clone a malicious repo locally or via --recurse-submodules with embedded bare repositories; Git fails to filter symbolic links during the object directory copy process, allowing unauthorized access to sensitive information on the victim's machine.
Summary generated and translated by AI from the official description.
Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the `--recurse-submodules` option. Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the `--local` optimization when on a shared machine, either by passing the `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively, avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global protocol.file.allow user`.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N