Vulnerability in github.com/MichaelMure/git-bug (CVE-2021-28955)
Summary
Vulnerability in github.com/MichaelMure/git-bug (CVE-2021-28955). Successful exploitation can lead to full system takeover. Exploitable via git.bat. Mitigation: upgrade to 0.7.2 or later.
Original description
The description as published by the source.
Impact
The go language recently addressed a security issue in the way that binaries are found before being executed. Some operating systems like Windows persist to have the current directory being part of the default search path, and having priority over the system-wide path.
This means that it's possible for a malicious user to craft for example a git.bat command, commit it and push it in a repository. Later when git-bug search for the git binary, this malicious executable can take priority and be executed.
Who is impacted
This issue happen on Windows and some other operating systems with a badly configured PATH.
All version prior to 0.7.2 are vulnerable to this issue.
Patches
Version 0.7.2 fix this issue. Users should update as soon as possible.
References
More details about this issue can be found here.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-28955 has been found in github.com/MichaelMure/git-bug.
Attackers can target a specific entry point like git.bat over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/MichaelMure/git-bug to 0.7.2 or later.
If unsure, ask your IT team or search "github.com/MichaelMure/git-bug CVE-2021-28955" on the vendor's site.
CVE-2021-28955 (github.com/MichaelMure/git-bug) — CWE-427
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: git.bat
Patched: 0.7.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-427) exists in github.com/MichaelMure/git-bug. Attackers reach the vulnerable code path via git.bat without authentication.
Check the vendor advisory for the affected versions of github.com/MichaelMure/git-bug. Attack surface: git.bat.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.7.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/MichaelMure/git-bug' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/MichaelMure/git-bug' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/MichaelMure/git-bugを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/MichaelMure/git-bug to 0.7.2ステージング環境で 0.7.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web vuln.ryotak.me