← Back
GHSA-v3f4-w7r7-v3hm
Vulnerability in @zenalexa/unicli (GHSA-v3f4-w7r7-v3hm)
Summary
vulnerability in @zenalexa/unicli (GHSA-v3f4-w7r7-v3hm). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.225.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-v3f4-w7r7-v3hm** has been found in @zenalexa/unicli.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @zenalexa/unicli to **0.225.2** or later.
If unsure, ask your IT team or search "@zenalexa/unicli GHSA-v3f4-w7r7-v3hm" on the vendor's site.
GHSA-v3f4-w7r7-v3hm (@zenalexa/unicli) — CWE-346 /
Patched: `0.225.2` — apply immediately
Workaround: Upgrade to 0.225.2 or later.
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.
❓ What is the problem
**A vulnerability** (CWE-346) exists in @zenalexa/unicli.
📍 Affected scope
@zenalexa/unicli — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.225.2**.
🛡️ Workaround
Workaround: Upgrade to 0.225.2 or later.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@zenalexa/unicli' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@zenalexa/unicli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@zenalexa/unicli` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to 0.225.2 or later.パッチが適用されるまでの応急処置として、Upgrade to 0.225.2 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @zenalexa/unicli to 0.225.2ステージング環境で 0.225.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@zenalexa/unicli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.225.2"}]}]