Undertow: improper state management in proxy protocol parsing causes information leakage
- 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 2.2.36.Final, 2.3.17.Final
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- undertow
fixed in 2.2.36.Final; From 2.3.0.Alpha1 · fixed in 2.3.17.Final
- undertow
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- io.undertow/undertow-core
Version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform 7
Version range not reported
- eap7-apache-commons-beanutils
Version range not reported
- eap7-hornetq
Version range not reported
- eap7-jboss-server-migration
Version range not reported
- eap7-undertow
Version range not reported
- eap7-wildfly
Version range not reported
- eap7-jackson-annotations
Version range not reported
- eap7-jackson-core
Version range not reported
- eap7-jackson-databind
Version range not reported
- eap7-jackson-jaxrs-providers
Version range not reported
- eap7-jackson-modules-base
Version range not reported
- eap7-jackson-modules-java8
Version range not reported
- eap7-netty
Version range not reported
- eap7-undertow
Version range not reported
- eap7-wildfly
Version range not reported
- eap7-undertow
Version range not reported
- eap7-wildfly
Version range not reported
- eap7-undertow
Version range not reported
- eap7-wildfly
Version range not reported
- undertow-core
Version range not reported
- eap8-amazon-ion-java
Version range not reported
- eap8-eap-product-conf-parent
Version range not reported
- eap8-undertow
Version range not reported
- eap8-wildfly
Version range not reported
- eap8-amazon-ion-java
Version range not reported
- eap8-eap-product-conf-parent
Version range not reported
- eap8-undertow
Version range not reported
- eap8-wildfly
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- quarkus-undertow
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- undertow-core
Version range not reported
- undertow-core
Version range not reported
- undertow
Version range not reported
- undertow
Version range not reported
- io.undertow:undertow-coreMaven
fixed in 2.2.36.Final
- io.undertow:undertow-coreMaven
From 2.3.0.Alpha1 · fixed in 2.3.17.Final