Summary
On Windows, git-sizer might run a git executable within the repository being analyzed
Workarounds
If you are on Windows, then either
- Don't run
git-sizeragainst a repository that might contain hostile code, or, if you must… - Run
git-sizeragainst a bare clone of the hostile repository, or, if that is not possible… - Make sure that the hostile repository doesn't have an executable in its top-level directory before running
git-sizer.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your PATH.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in the
git-sizerproject. - Email us at GitHub support.
Impact
On Windows, if git-sizer is run against a non-bare repository, and that repository has an executable called git.exe, git.bat, etc., then that executable might be run by git-sizer rather than the system git executable. An attacker could try to use social engineering to get a victim to run git-sizer against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's PATH has the current directory before the path to the standard git executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Users should update to git-sizer v1.4.0
Frequently Asked Questions
- What is GHSA-57Q7-RXQQ-7VGP? GHSA-57Q7-RXQQ-7VGP is a medium-severity security vulnerability in github.com/github/git-sizer (go), affecting versions <= 1.3.0. It is fixed in 1.4.0.
- Which versions of github.com/github/git-sizer are affected by GHSA-57Q7-RXQQ-7VGP? github.com/github/git-sizer (go) versions <= 1.3.0 is affected.
- Is there a fix for GHSA-57Q7-RXQQ-7VGP? Yes. GHSA-57Q7-RXQQ-7VGP is fixed in 1.4.0. Upgrade to this version or later.
- Is GHSA-57Q7-RXQQ-7VGP exploitable, and should I be worried? Whether GHSA-57Q7-RXQQ-7VGP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-57Q7-RXQQ-7VGP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-57Q7-RXQQ-7VGP? Upgrade
github.com/github/git-sizerto 1.4.0 or later.