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