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