← Back
GHSA-hc4m-q9jh-xw4j
Vulnerability in nono-cli (GHSA-hc4m-q9jh-xw4j)
Summary
vulnerability in nono-cli (GHSA-hc4m-q9jh-xw4j). Risk of unauthorized operations or information disclosure. Exploitable via ``verify_profile_packs``. Mitigation: upgrade to `0.61.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-hc4m-q9jh-xw4j** has been found in nono-cli.
Attackers can target a specific entry point like ``verify_profile_packs`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade nono-cli to **0.61.3** or later.
If unsure, ask your IT team or search "nono-cli GHSA-hc4m-q9jh-xw4j" on the vendor's site.
GHSA-hc4m-q9jh-xw4j (nono-cli) — CWE-636 /
Attack surface: `verify_profile_packs`
Patched: `0.61.3` — 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.
❓ What is the problem
**A vulnerability** (CWE-636) exists in nono-cli. Attackers reach the vulnerable code path via ``verify_profile_packs`` without authentication.
📍 Affected scope
nono-cli — . Attack surface: `verify_profile_packs`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.61.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'nono-cli' .` 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 'nono-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nono-cli` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade nono-cli to 0.61.3ステージング環境で 0.61.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
nono-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.61.3"}]}]