← Back
CVE-2022-1930
Vulnerability in eth-account (CVE-2022-1930)
Summary
vulnerability in eth-account (CVE-2022-1930). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.5.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-1930** has been found in eth-account.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade eth-account to **0.5.9** or later.
If unsure, ask your IT team or search "eth-account CVE-2022-1930" on the vendor's site.
CVE-2022-1930 (eth-account) — CWE-1333 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.5.9` — 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-1333) exists in eth-account.
📍 Affected scope
eth-account — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.5.9**.
🛡️ 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 'eth-account' .` 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 'eth-account' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `eth-account` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade eth-account to 0.5.9ステージング環境で 0.5.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
eth-account
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.9"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-1930
- advisory https://github.com/advisories/GHSA-v65g-f3cj-fjp4
- package https://github.com/ethereum/eth-account
- package https://pypi.org/project/eth-account
- web https://github.com/ethereum/eth-account/commit/70f89be700df0d5f08ef696252c88741f8414060
- web https://research.jfrog.com/vulnerabilities/eth-account-redos-xray-248681