CVE-2019-11072 (https://nvd.nist.gov/vuln/detail/CVE-2019-11072): ** DISPUTED ** 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."
Note that the dispute is about the severity of the bug. It still seems valid. It can still cause a denial of service - and only with a non-default config option, but nothing more serious.
@maintainer(s): ping
I'll go ahead in a few days if no objections? Doing 1.4.55 because it fixes a small OOB read.
arm stable
ppc stable
sparc stable
ppc64 stable
amd64 stable
x86 stable
s390 stable
