Security Advisory

CVE-2019-11072: lighttpd %2F Decoding Overflow

Last updated:
  • CVE-2019-11072

CVE-2019-11072 is a signed integer overflow in the URL normalisation of lighttpd 1.4.50 to 1.4.53 that a GET request containing /%2F? triggers when the non-default url-path-2f-decode option is on. NVD scores it 9.8, but the record is disputed: the lighttpd developer says the effect is an abort and server exit. Version 1.4.54 fixes it.

Vulnerability summary

CVSS base score

9.8

Critical severity

EPSS score (FIRST)

73.8%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-11072 · Source: NVD

Affected components

ComponentCPEVersion range
lighttpd (server.http-parseopts url-path-2f-decode)cpe:2.3:a:lighttpd:lighttpd:*:*:*:*:*:*:*:*through 1.4.53 per NVD; the option exists from 1.4.50; fixed in 1.4.54
Wind River Linux LTS 18 (lighttpd package)—fixed in 10.18.44.6; Wind River Linux 8, 9, LTS 17 and LTS 19 not vulnerable (Wind River Linux security bulletin 2020-05-11, LIN1018-3900)
OpenWrt packages feed, openwrt-19.07 branch (lighttpd 1.4.53)—1.4.53 from 2019-03-16; 1.4.54 merged 2019-09-07

What does this mean for affected devices?

CVE-2019-11072 is an integer overflow (CWE-190) in burl_normalize_2F_to_slash_fix in burl.c. NVD's record says 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?". NVD scores it 9.8 under CVSS v3.0, vector CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, and the record carries a disputed tag (NVD).

The dispute is in the same record. The developer states that the feature "is a new feature in lighttpd 1.4.50, and is not enabled by default", that certain input "will trigger an abort() in lighttpd when that feature is enabled", and that "this is not exploitable beyond triggering the explicit abort() with subsequent application exit". So for triage this is a remote crash on servers that enabled url-path-2f-decode, not the code execution the 9.8 vector implies. The fix commit, dated 2019-04-10, is titled "fix abort in http-parseopts" and names "url-path-2f-decode enabled" as the trigger; it shipped in lighttpd 1.4.54 on 2019-05-27. That release also turned strict URL parsing on by default, so check the effective settings, not only the configuration file, on 1.4.50 to 1.4.53 builds.

Two embedded Linux distributions show how narrow the window was. The Wind River Linux security bulletin of 2020-05-11 lists only LTS 18 as affected, fixed in 10.18.44.6 under defect LIN1018-3900, with Wind River Linux 8, 9, LTS 17 and LTS 19 not vulnerable. The OpenWrt packages feed for 19.07 shipped lighttpd 1.4.53 from 2019-03-16 until commit 19039dc, "Fixes CVE-2019-11072", moved it to 1.4.54 on 2019-09-07. Debian's tracker marks jessie and stretch as not affected because the code is newer. Our embedded web server vulnerabilities guide explains how to read lighttpd versions and module settings out of a firmware image.

The CVE is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.7376, the 99.5th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS). A high EPSS score with a disputed, crash-only impact is a case where our KEV and EPSS prioritisation guide suggests reading the record before ranking it.

Upgrade lighttpd to 1.4.54 or later. On 1.4.50 to 1.4.53, leave url-path-2f-decode out of server.http-parseopts; a device that never enabled it can record CVE-2019-11072 as not affected in its VEX statement. CVE-2018-19052 is the lighttpd path traversal fixed one release line earlier.

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • lighttpd before 1.4.54 signed integer overflow in burl_normalize_2F_to_slash_fix via /%2F?; NVD CVSS v3.0 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); CWE-190; tagged disputed; developer: feature new in 1.4.50, not enabled by default, explicit abort() only. — NVD
  • Fix commit 32120d5 (2019-04-10): "fix abort in http-parseopts", "url-path-2f-decode enabled". — lighttpd commit 32120d5
  • 1.4.54 released 2019-05-27; includes "[core] fix abort in http-parseopts (fixes #2945)"; strict URL parsing and normalization by default. — lighttpd 1.4.54 release notes
  • CVE-2019-11072 lighttpd: only WRLinux LTS 18 affected, fixed 10.18.44.6; 8, 9, LTS 17, LTS 19 not vulnerable; defect LIN1018-3900. — Wind River Linux security bulletin 2020-05-11
  • openwrt-19.07 packages: lighttpd 1.4.53 from 2019-03-16; commit 19039dc "Update to version 1.4.54 / Fixes CVE-2019-11072" committed 2019-09-07. — OpenWrt packages commit 19039dc
  • Debian jessie and stretch not affected (code introduced later). — Debian Security Tracker
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.73762 (99.5th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. lighttpd commit 32120d5: [core] fix abort in http-parseopts
  3. lighttpd 1.4.54 release notes
  4. Wind River Linux 2020-05-11 Security Bulletin
  5. OpenWrt packages commit 19039dc: lighttpd: Update to version 1.4.54
  6. Debian Security Tracker
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Why is CVE-2019-11072 marked as disputed?

The lighttpd developer states that the abused feature is new in 1.4.50, is not enabled by default, and that bad input only triggers an explicit abort() and server exit, not code execution, while NVD scores it 9.8 (per NVD).

Which lighttpd setting does CVE-2019-11072 need?

The url-path-2f-decode option of server.http-parseopts must be enabled. The fix commit names it as the trigger, and the option only exists from lighttpd 1.4.50 (per the lighttpd fix commit and NVD).

Which embedded Linux releases shipped an affected lighttpd?

Wind River lists only Wind River Linux LTS 18, fixed in 10.18.44.6, and the OpenWrt 19.07 packages branch carried lighttpd 1.4.53 until 1.4.54 was merged on 2019-09-07 (per the Wind River Linux 2020-05-11 bulletin and OpenWrt packages commit 19039dc).

Is CVE-2019-11072 known to be exploited?

It is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.7376, the 99.5th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).