-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vulndb: potential Go vuln in github.com/git/git: CVE-2022-39253 #1068
Labels
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
Comments
tatianab
added
NeedsTriage
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
and removed
NeedsTriage
labels
Oct 19, 2022
Change https://go.dev/cl/443646 mentions this issue: |
This was referenced Jan 18, 2023
This was referenced Feb 14, 2023
This was referenced Apr 25, 2023
This was referenced Nov 8, 2023
This was referenced May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CVE-2022-39253 references github.com/git/git, which may be a Go module.
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 togit clone
or cloning from a URL that uses thefile://
scheme. Alternatively, avoid cloning repositories from untrusted sources with--recurse-submodules
or rungit config --global protocol.file.allow user
.References:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: