Undertow up to 1.3.30/1.4.16/2.0.0.Alpha1 Incomplete Fix CVE-2017-2666 HTTP Request HTTP Poisoning request smuggling

Summaryinfo

A vulnerability labeled as critical has been found in Undertow up to 1.3.30/1.4.16/2.0.0.Alpha1. Affected by this vulnerability is an unknown functionality of the component Incomplete Fix CVE-2017-2666. Such manipulation as part of HTTP Request leads to request smuggling (HTTP Poisoning). This vulnerability is documented as CVE-2017-7559. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Undertow up to 1.3.30/1.4.16/2.0.0.Alpha1. It has been rated as critical. Affected by this issue is an unknown part of the component Incomplete Fix CVE-2017-2666. The manipulation as part of a HTTP Request leads to a request smuggling vulnerability (HTTP Poisoning). Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In Undertow 2.x before 2.0.0.Alpha2, 1.4.x before 1.4.17.Final, and 1.3.x before 1.3.31.Final, it was found that the fix for CVE-2017-2666 was incomplete and invalid characters are still allowed in the query string and path parameters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.

The bug was discovered 08/15/2017. The weakness was released 01/10/2018 (Website). The advisory is shared for download at access.redhat.com. This vulnerability is handled as CVE-2017-7559 since 04/05/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 120 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 105268 (RHEL 6 : JBoss EAP (RHSA-2017:3454)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236580 (Red Hat Update for JBoss Enterprise Application Platform 7.1.0 (RHSA-2017:3455)).

Upgrading to version 1.3.31, 1.4.17 or 2.0.0.Alpha2 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (105268). Entries connected to this vulnerability are available at VDB-92173, VDB-92175, VDB-92322 and VDB-95800. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Undertow

Version

• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.3.4
• 1.3.5
• 1.3.6
• 1.3.7
• 1.3.8
• 1.3.9
• 1.3.10
• 1.3.11
• 1.3.12
• 1.3.13
• 1.3.14
• 1.3.15
• 1.3.16
• 1.3.17
• 1.3.18
• 1.3.19
• 1.3.20
• 1.3.21
• 1.3.22
• 1.3.23
• 1.3.24
• 1.3.25
• 1.3.26
• 1.3.27
• 1.3.28
• 1.3.29
• 1.3.30
• 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
• 2.0.0.Alpha1

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion