OpenLiteSpeed before 1.8.1 mishandles chunked encoding.
CVE-2024-31617
Score 5.3 from GitHub Security Advisory published 2024-05-22. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
May 22, 2024
Last Modified
June 5, 2025
References (2)
- cve@mitrehttps://github.com/litespeedtech/openlitespeed/releases/tag/v1.8.1
- af854a3a-2127-422b-91ae-364da2661108https://github.com/litespeedtech/openlitespeed/releases/tag/v1.8.1
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2024-31617?
When was CVE-2024-31617 disclosed?
Is CVE-2024-31617 actively exploited?
What is the CVSS score of CVE-2024-31617?
How do I remediate CVE-2024-31617?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-31617
Is Your Infrastructure Affected by CVE-2024-31617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.