← Back
CVE-2024-32481
Vulnerability in vyper (CVE-2024-32481)
Summary
vulnerability in vyper (CVE-2024-32481). Risk of unauthorized operations or information disclosure. Exploitable via ``range``. Mitigation: upgrade to `0.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-32481** has been found in vyper.
Attackers can target a specific entry point like ``range`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade vyper to **0.4.0** or later.
If unsure, ask your IT team or search "vyper CVE-2024-32481" on the vendor's site.
CVE-2024-32481 (vyper) — CWE-681 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `range` / `start` / `sle`
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.
❓ What is the problem
**A vulnerability** (CWE-681) exists in vyper. Attackers reach the vulnerable code path via ``range`` without authentication.
📍 Affected scope
vyper — . Attack surface: `range` / `start` / `sle`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.4.0**.
🛡️ 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 'vyper' .` 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 'vyper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vyper` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade vyper to 0.4.0ステージング環境で 0.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
vyper
[{"type":"ECOSYSTEM","events":[{"introduced":"0.3.8"},{"fixed":"0.4.0"}]}]
References
- advisory https://github.com/advisories/GHSA-ppx5-q359-pvwj
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-32481
- package https://github.com/vyperlang/vyper
- web https://github.com/vyperlang/vyper/security/advisories/GHSA-ppx5-q359-pvwj
- web https://github.com/vyperlang/vyper/commit/3de1415ee77a9244eb04bdb695e249d3ec9ed868
- web https://github.com/vyperlang/vyper/commit/5319cfbe14951e007ccdb323257e5ada869b35d5
- web https://github.com/vyperlang/vyper/blob/9136169468f317a53b4e7448389aa315f90b95ba/vyper/codegen/stmt.py#L286-L287