CVE-2024-28871 json
Excessive CPU used on malformed traffic
published 2y ago modified 4mo ago also EUVD-2024-25941
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
LibHTP is a security-aware parser for the HTTP protocol and the related bits and pieces. Version 0.5.46 may parse malformed request traffic, leading to excessive CPU usage. Version 0.5.47 contains a patch for the issue. No known workarounds are available.
Patch / fix
- libhtp Debian 13 1:0.5.47-1
debian advisories DEBIAN-CVE-2024-28871
- libhtp Ubuntu Pro 20.04 LTS 1:0.5.32-1ubuntu0.1~esm1
- libhtp Ubuntu Pro 22.04 LTS 1:0.5.39-1ubuntu0.1~esm1
- libhtp Ubuntu Pro 24.04 LTS 1:0.5.46-1ubuntu2+esm1
ubuntu advisories UBUNTU-CVE-2024-28871
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- libhtp openSUSE Tumbleweed 0.5.48-2.1
opensuse advisories openSUSE-SU-2024:14016-1
- github.com/OISF/libhtp@79e713f commit
- github.com/OISF/libhtp@bf618ec commit
Is CVE-2024-28871 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- OISF libhtp
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
Sources
- CVE List CVE-2024-28871
- NVD CVE-2024-28871
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.