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