Homepage

Link Following Affecting git-core-doc package, versions <0:2.38.1-1.amzn2.0.1

Severity

 Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.1% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2-GITCOREDOC-3159970
  • published7 Dec 2022
  • disclosed19 Oct 2022
Report a new vulnerability Found a mistake?

Introduced: 19 Oct 2022

CVE-2022-39253  (opens in a new tab)
CWE-59  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 git-core-doc to version 0:2.38.1-1.amzn2.0.1 or higher.
This issue was patched in ALAS2-2022-1886.

NVD Description

Note: Versions mentioned in the description apply only to the upstream git-core-doc package and not the git-core-doc package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1