Skip to content

GHSA-p9w3-gwc2-cr49 CVE-2020-10687

HTTP Request Smuggling in Undertow

Medium Maven
Severity
4.8 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.23%
Chance of exploitation in the next 30 days. Higher than 68.96% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Fix
2.2.0.Final
Upgrade io.undertow:undertow-core to this version or later

Description

A flaw was discovered in all versions of Undertow before Undertow 2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own.

Affected versions

Maven

PackageVulnerableFixed in
io.undertow:undertow-core
< 2.2.0.Final
2.2.0.Final

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 → 2.2.0.Final

maven
<dependency><groupId>io.undertow</groupId><artifactId>undertow-core</artifactId><version>2.2.0.Final</version></dependency>
gradle
implementation("io.undertow:undertow-core:2.2.0.Final")

Severity breakdown

CVSS 3.1 4.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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