Skip to content
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-2021-21300 #2320

Closed
tatianab opened this issue Nov 8, 2023 · 1 comment
Closed

x/vulndb: potential Go vuln in github.com/git/git: CVE-2021-21300 #2320

tatianab opened this issue Nov 8, 2023 · 1 comment
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process

Comments

@tatianab
Copy link
Contributor

tatianab commented Nov 8, 2023

CVE-2021-21300 references github.com/git/git, which may be a Go module.

Description:
Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

References:

Cross references:

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

modules:
    - module: github.com/git/git
      vulnerable_at: 2.42.1+incompatible
      packages:
        - package: git
cves:
    - CVE-2021-21300
references:
    - advisory: https://github.com/git/git/security/advisories/GHSA-8prw-h3cq-mghm
    - web: https://lore.kernel.org/git/[email protected]/
    - web: https://git-scm.com/docs/git-config#Documentation/git-config.txt-coresymlinks
    - web: https://git-scm.com/docs/gitattributes#_filter
    - fix: https://github.com/git/git/commit/684dd4c2b414bcf648505e74498a608f28de4592
    - web: http://www.openwall.com/lists/oss-security/2021/03/09/3
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/LCLJJLKKMS5WRFO6C475AOUZTWQLIARX/
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/LMXX2POK5X576BSDWSXGU7EIK6I72ERU/
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/BBPNGLQSYJHLZZ37BO42YY6S5OTIF4L4/
    - web: https://support.apple.com/kb/HT212320
    - web: http://seclists.org/fulldisclosure/2021/Apr/60
    - web: https://security.gentoo.org/glsa/202104-01
    - web: http://packetstormsecurity.com/files/163978/Git-LFS-Clone-Command-Execution.html
    - web: https://lists.debian.org/debian-lts-announce/2022/10/msg00014.html

@tatianab tatianab added the excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process label Nov 8, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/540721 mentions this issue: data/excluded: batch add 135 excluded reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process
Projects
None yet
Development

No branches or pull requests

2 participants