# CVE-2024-23837: LibHTP unbounded folded header handling leads to denial service

> Crafted HTTP traffic causes excessive processing time in LibHTP, leading to denial of service for applications using the library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-23837, GHSA-f9wf-rrjj-qx8m, UBUNTU-CVE-2024-23837, openSUSE-SU-2024:0150-1, openSUSE-SU-2024:0150-2, openSUSE-SU-2024:13706-1

## What is CVE-2024-23837?

CVE-2024-23837 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LibHTP is a security-aware parser for the HTTP protocol. Crafted traffic can cause excessive processing time of HTTP headers, leading to denial of service. This issue is addressed in 0.5.46.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2024-23837?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libhtp` | SUSE:Package Hub 15 SP5 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | SUSE:Package Hub 15 SP5 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | SUSE:Package Hub 15 SP6 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | SUSE:Package Hub 15 SP6 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | openSUSE:Leap 15.5 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | openSUSE:Leap 15.5 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | openSUSE:Leap 15.6 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | openSUSE:Leap 15.6 | All versions | 0.5.42-bp156.3.3.1 |
| `libhtp` | openSUSE:Tumbleweed | All versions | 0.5.46-1.1 |

Products: Fedoraproject Fedora, Oisf Libhtp.

## How do I fix CVE-2024-23837?

Upgrade to a fixed version.

## Is CVE-2024-23837 being exploited?

There is no known exploitation of CVE-2024-23837 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23837 and fix it if it is affected.

What it is: CVE-2024-23837 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23837 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23837/ (Markdown: https://insights.sbomify.com/CVE-2024-23837/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23837
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23837
- OSV: https://osv.dev/vulnerability/CVE-2024-23837

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23837/
Summaries are generated and may contain mistakes; the official description above is the record.