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