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 w
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.17.Final, 1.3.31.Final, 2.0.0.Alpha2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Red Hat, Inc. undertow
2.x before 2.0.0.Alpha2, 1.4.x before 1.4.17.Final, 1.3.x before 1.3.31.Final
- io.undertow:undertow-coreMaven
From 1.4.0 · fixed in 1.4.17.Final
- io.undertow:undertow-coreMaven
From 1.3.0 · fixed in 1.3.31.Final
- io.undertow:undertow-coreMaven
From 2.0.0.Alpha1 · fixed in 2.0.0.Alpha2