lighttpd up to 1.4.53 burl.c burl_normalize_2F_to_slash_fix HTTP GET Request integer overflow ⚔ [Disputed]

Summaryinfo

A vulnerability categorized as critical has been discovered in lighttpd up to 1.4.53. Affected is the function burl_normalize_2F_to_slash_fix of the file burl.c. Executing a manipulation with the input /%2F as part of HTTP GET Request can lead to integer overflow. This vulnerability is registered as CVE-2019-11072. It is possible to launch the attack remotely. No exploit is available. The actual existence of this vulnerability is currently in question. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in lighttpd up to 1.4.53 (Web Server) and classified as critical. This vulnerability affects the function burl_normalize_2F_to_slash_fix of the file burl.c. The manipulation with the input value /%2F leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The bug was discovered 04/10/2019. The weakness was published 04/10/2019 (Website). The advisory is available at securityfocus.com. This vulnerability was named CVE-2019-11072 since 04/10/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.

The real existence of this vulnerability is still doubted at the moment.

Upgrading to version 1.4.54 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Web Server

Name

• lighttpd

Version

• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.4.6
• 1.4.7
• 1.4.8
• 1.4.9
• 1.4.10
• 1.4.11
• 1.4.12
• 1.4.13
• 1.4.14
• 1.4.15
• 1.4.16
• 1.4.17
• 1.4.18
• 1.4.19
• 1.4.20
• 1.4.21
• 1.4.22
• 1.4.23
• 1.4.24
• 1.4.25
• 1.4.26
• 1.4.27
• 1.4.28
• 1.4.29
• 1.4.30
• 1.4.31
• 1.4.32
• 1.4.33
• 1.4.34
• 1.4.35
• 1.4.36
• 1.4.37
• 1.4.38
• 1.4.39
• 1.4.40
• 1.4.41
• 1.4.42
• 1.4.43
• 1.4.44
• 1.4.45
• 1.4.46
• 1.4.47
• 1.4.48
• 1.4.49
• 1.4.50
• 1.4.51
• 1.4.52
• 1.4.53

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion