OS Command Injection in @thi.ng/egf (CVE-2021-21412)
Summary
OS command injection in @thi.ng/egf (CVE-2021-21412). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.4.0 or later.
Original description
The description as published by the source.
Impact
Potential for arbitrary code execution in #gpg-tagged property values (only if decrypt: true option is enabled)
Patches
A fix has already been released as v0.4.0
Workarounds
By default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).
However, if GPG encrypted values are used/required:
- Perform a regex search for
#gpg-tagged values in the EGF source file/string and check for backtick (`) chars in the encrypted value string - Replace/remove them or skip parsing if present...
References
https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261
For more information
If you have any questions or comments about this advisory, please open an issue in the thi.ng/umbrella repo, of which this package is part of.
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-21412 has been found in @thi.ng/egf.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @thi.ng/egf to 0.4.0 or later.
If unsure, ask your IT team or search "@thi.ng/egf CVE-2021-21412" on the vendor's site.
CVE-2021-21412 (@thi.ng/egf) — CWE-78
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.4.0 — 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 @thi.ng/egf.
Check the vendor advisory for the affected versions of @thi.ng/egf.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.4.0.
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 '@thi.ng/egf' . 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 '@thi.ng/egf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@thi.ng/egfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @thi.ng/egf to 0.4.0ステージング環境で 0.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web npmjs.com