OS Command Injection in reg-keygen-git-hash-plugin (CVE-2021-32673)
Summary
OS command injection in reg-keygen-git-hash-plugin (CVE-2021-32673). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.10.16 or later.
Original description
The description as published by the source.
reg-keygen-git-hash-plugin is a reg-suit plugin to detect the snapshot key to be compare with using Git commit hash. reg-keygen-git-hash-plugin through and including 0.10.15 allow remote attackers to execute of arbitrary commands. Upgrade to version 0.10.16 or later to resolve this issue.
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-32673 has been found in reg-keygen-git-hash-plugin.
Successful exploitation can lead to full system takeover.
What to do: upgrade reg-keygen-git-hash-plugin to 0.10.16 or later.
If unsure, ask your IT team or search "reg-keygen-git-hash-plugin CVE-2021-32673" on the vendor's site.
CVE-2021-32673 (reg-keygen-git-hash-plugin) — CWE-78
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.10.16 — 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.
OS command injection (CWE-78) exists in reg-keygen-git-hash-plugin.
Check the vendor advisory for the affected versions of reg-keygen-git-hash-plugin.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.10.16.
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 'reg-keygen-git-hash-plugin' . 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 'reg-keygen-git-hash-plugin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
reg-keygen-git-hash-pluginを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade reg-keygen-git-hash-plugin to 0.10.16ステージング環境で 0.10.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory npmjs.com
- patch github.com