← Back
GHSA-3whf-vgf2-9w6g
Vulnerability in zaino-state (GHSA-3whf-vgf2-9w6g)
Summary
vulnerability in zaino-state (GHSA-3whf-vgf2-9w6g). Risk of unauthorized operations or information disclosure. Exploitable via ``previous_block_hash``. Mitigation: upgrade to `0.4.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-3whf-vgf2-9w6g** has been found in zaino-state.
Attackers can target a specific entry point like ``previous_block_hash`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade zaino-state to **0.4.1** or later.
If unsure, ask your IT team or search "zaino-state GHSA-3whf-vgf2-9w6g" on the vendor's site.
GHSA-3whf-vgf2-9w6g (zaino-state) — CWE-770 /
Attack surface: `previous_block_hash` / `handle_reorg` / `working_snapshot.blocks` / `B.hash`
Patched: `0.4.1` — 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-770) exists in zaino-state. Attackers reach the vulnerable code path via ``previous_block_hash`` without authentication.
📍 Affected scope
zaino-state — . Attack surface: `previous_block_hash` / `handle_reorg` / `working_snapshot.blocks` / `B.hash`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.4.1**.
🛡️ 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 'zaino-state' .` 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 'zaino-state' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zaino-state` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade zaino-state to 0.4.1ステージング環境で 0.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
zaino-state
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1"}]}]
References
- web https://github.com/zingolabs/zaino/security/advisories/GHSA-3whf-vgf2-9w6g
- web https://github.com/zingolabs/zaino/pull/1172
- web https://github.com/zingolabs/zaino/commit/428822509bc722eb9727681752686ede9bc87e77
- web https://github.com/zingolabs/zaino/commit/d874295f1377bec7fd712ef75b364181b8c77d46
- web https://github.com/zingolabs/zaino/commit/e05112aac54ec3cdb6da29fbc143ea710b32f009
- web https://github.com/advisories/GHSA-3whf-vgf2-9w6g