CVE-2022-39253 Git subject to exposure of sensitive information via local clone of symbolic links

Medium 5.5 Published Updated

Attackers can expose sensitive local files by tricking victims into cloning malicious repositories with symbolic links in the objects directory.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2022-39253?

CVE-2022-39253 is a medium-severity vulnerability in Apple Xcode, published on 19 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

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

Weakness: CWE-59, CWE-200

Which versions are affected by CVE-2022-39253?

It affects 4 products.

Linux distribution packages (3)
docker-compose openSUSE:TumbleweedAll versions2.12.2-1.1
perl-Git-Repository openSUSE:TumbleweedAll versions1.326.0-1.1
reuse openSUSE:TumbleweedAll versions1.1.2-1.1

Products include Apple Xcode, Debian Debian Linux, Fedoraproject Fedora, Git-Scm Git.

How do I fix CVE-2022-39253?

Upgrade to a fixed version.

Is CVE-2022-39253 being exploited?

There is no known exploitation of CVE-2022-39253 in the wild and no public exploit code.

Public exploit code: 2 proofs of concept on GitHub.

All Apple Xcode vulnerabilities

Sources

Also known as ALPINE-CVE-2022-39253, CLEANSTART-2024-XV18933, CLEANSTART-2026-DU64203, CLEANSTART-2026-ZJ93716, CLSA-2023-1681137249, DEBIAN-CVE-2022-39253 and 6 more.

Is CVE-2022-39253 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free