Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

x/vulndb: potential Go vuln in github.com/git/git: CVE-2022-39253 #1068

Closed
GoVulnBot opened this issue Oct 19, 2022 · 1 comment
Closed
Labels
excluded: NOT_GO_CODE This vulnerability does not refer to a Go module.

Comments

@GoVulnBot
Copy link

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 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:

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/git/git
    packages:
      - package: git
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`. \n"
cves:
  - CVE-2022-39253
references:
  - web: https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85

@tatianab tatianab added NeedsTriage excluded: NOT_GO_CODE This vulnerability does not refer to a Go module. and removed NeedsTriage labels Oct 19, 2022
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/443646 mentions this issue: data/excluded: add GO-2022-1068.yaml for CVE-2022-39253

@tatianab tatianab reopened this Oct 24, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
excluded: NOT_GO_CODE This vulnerability does not refer to a Go module.
Projects
None yet
Development

No branches or pull requests

3 participants