# CVE-2019-11072: Integer overflow in n/a

> Remote attackers can cause a denial of service via integer overflow in lighttpd when a specific non-default feature is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 10 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11072, GHSA-59gp-rjv5-p2h6

## What is CVE-2019-11072?

CVE-2019-11072 is a critical vulnerability in n/a, published on 10 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a malicious HTTP GET request, as demonstrated by mishandling of /%2F? in burl_normalize_2F_to_slash_fix in burl.c. NOTE: The developer states "The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf). Certain input will trigger an abort() in lighttpd when that feature is enabled. lighttpd detects the underflow or realloc() will fail (in both 32-bit and 64-bit executables), also detected in lighttpd. Either triggers an explicit abort() by lighttpd. This is not exploitable beyond triggering the explicit abort() with subsequent application exit.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2019-11072?

It affects 1 product.


Products: Lighttpd Lighttpd.

## How do I fix CVE-2019-11072?

Upgrade to a fixed version.

## Is CVE-2019-11072 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11072 exists.

## Other vulnerabilities in n/a

- [CVE-2007-3949](https://insights.sbomify.com/CVE-2007-3949/): Security feature bypass in n/a (high 8.3)
- [CVE-2007-1870](https://insights.sbomify.com/CVE-2007-1870/): Null dereference in n/a (high 7.8)
- [CVE-2022-30780](https://insights.sbomify.com/CVE-2022-30780/): Denial of service in n/a (high 7.5)
- [CVE-2025-12642](https://insights.sbomify.com/CVE-2025-12642/): HTTP Header Smuggling via Trailer Merge (medium 6.9)
- [CVE-2007-4727](https://insights.sbomify.com/CVE-2007-4727/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11072 and fix it if it is affected.

What it is: CVE-2019-11072 is a critical vulnerability in n/a, published on 10 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11072 exists.

Affected product: n/a. 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-2019-11072/ (Markdown: https://insights.sbomify.com/CVE-2019-11072/index.md)
```

## Sources

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

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