github.com/github/git-sizer
Affected
- introduced
0, fixed1.4.0(semver)
Fixed versions
1.4.0
Fix
- Fixed version
1.4.0go get github.com/github/[email protected]
Advisory
Also known as: GO-2022-0424
On Windows, git-sizer might run a git executable within the repository being analyzed
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.
Patches
Users should update to git-sizer v1.4.0
Workarounds
If you are on Windows, then either
git-sizer against a repository that might contain hostile code, or, if you must…git-sizer against a bare clone of the hostile repository, or, if that is not possible…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:
Medium Basis: The source's own band: MODERATE
0, fixed 1.4.0 (semver)1.4.0
1.4.0go get github.com/github/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0