GHSA-5gg7-5wv8-4gcj CVE-2017-12165
Undertow Request Smuggling vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 1.86%
- Chance of exploitation in the next 30 days. Higher than 79.22% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
- Fix
1.3.31- Upgrade io.undertow:undertow-core to this version or later
Description
It was discovered that Undertow before 1.4.17, 1.3.31 and 2.0.0 processes http request headers with unusual whitespaces which can cause possible http request smuggling.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| io.undertow:undertow-core | < 1.3.31 |
1.3.31 |
| io.undertow:undertow-core | >= 1.4.0, < 1.4.17 |
1.4.17 |
| io.undertow:undertow-core | >= 2.0.0.Alpha1, < 2.0.0.Beta1 |
2.0.0.Beta1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
io.undertow:undertow-core Maven → 1.3.31
- maven
<dependency><groupId>io.undertow</groupId><artifactId>undertow-core</artifactId><version>1.3.31</version></dependency>- gradle
implementation("io.undertow:undertow-core:1.3.31")
Severity breakdown
CVSS 3.0 7.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Weakness
CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
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.
How to prevent it
- Implementation: Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
- Implementation: Use only SSL communication.
- Implementation: Terminate the client session after each request.
- System Configuration: Turn all pages to non-cacheable.
References
Advisories
Packages
Other links
- github.com/undertow-io/undertow/commit/1e72647818c9fb31b693a953b1ae595a6c82eb7f
- github.com/undertow-io/undertow/commit/5b008b7ac312c6cdb76679ff58c43620bb79d44f
- github.com/undertow-io/undertow/commit/691440ee58259fba76711b60d56dde6679808bdc
- bugzilla.redhat.com/show_bug.cgi
- issues.redhat.com/browse/UNDERTOW-1251
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-3x3v-w654-m28m Undertow: Denial of Service via Multipart/Form-Data Parsing on HTTP GET Requests | Medium | Also affects io.undertow:undertow-core |
| GHSA-33hj-rcmx-86mv Undertow Servlets Vulnerable to Remote DoS via OutOfMemoryError when Passed Large Parameter Names | High | Also affects io.undertow:undertow-core |
| GHSA-j382-5jj3-vw4j Undertow HTTP server core doesn't properly validate the Host header in incoming HTTP requests | Critical | Also affects io.undertow:undertow-core |
| GHSA-6h4f-pj3g-q8fq Undertow OutOfMemory when parsing form data encoding with application/x-www-form-urlencoded | High | Also affects io.undertow:undertow-core |
| GHSA-95h4-w6j8-2rp8 Undertow MadeYouReset HTTP/2 DDoS Vulnerability | High | Also affects io.undertow:undertow-core |
| GHSA-3jrv-jgp8-45v3 Undertow incorrectly parses cookies | High | Also affects io.undertow:undertow-core |
| GHSA-97cq-f4jm-mv8h Undertow Denial of Service vulnerability | High | Also affects io.undertow:undertow-core |
| GHSA-9623-mqmm-5rcf Undertow vulnerable to Race Condition | High | Also affects io.undertow:undertow-core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor