Patchfirst
CVE-2019-11072 EPSS 73.8%

lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service…

No fixed version listed yet.Check the vendor advisory. References ↓

Summary

The lighttpd web server, before version 1.4.54, contains a signed integer overflow in the URL normalisation code (burl_normalize_2F_to_slash_fix in burl.c) that handles encoded "/%2F" sequences. A remote attacker can send a malicious HTTP GET request to crash the server, but this requires the feature introduced in lighttpd 1.4.50 to be explicitly enabled in the configuration, as it is not on by default.

Official description · CVE.org

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.

Breakdown
20.6 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Disclosed on 10 Apr 2019. No public exploit code or confirmed exploitation is recorded.

What security researchers reported

Not named in any threat report yet

Also mentioned in 1 community threat pulse (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

3 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close