LiveActive security incident?Get immediate response
CVE Record

CVE-2024-7885: Undertow: improper state management in proxy protocol parsing causes information leakage

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Undertow can accidentally reuse proxy-protocol parsing data across requests sharing one HTTP connection. The most clearly supported outcome is errors and terminated connections, creating a remotely reachable availability risk. The source also describes possible unintended data exposure, but its CVSS assessment records no confidentiality impact.

Executive priority

Treat as a high-priority availability issue for exposed, affected Undertow deployments, especially supported JBoss EAP 7.3 EUS systems using Proxy Protocol. Schedule vendor updates promptly. Escalate confidentiality concerns only if environment-specific testing or vendor evidence confirms cross-request disclosure; the supplied CVSS score does not claim confidentiality loss.

Technical view

ProxyProtocolReadListener reuses one StringBuilder while parseProxyProtocolV1 handles multiple requests on a persistent connection. Stale data may therefore influence later parsing or be reused across request boundaries. The issue is classified as CWE-362 and scored CVSS 3.1 7.5: network-accessible, low complexity, unauthenticated, with high availability impact.

Likely exposure

Exposure is most plausible where Undertow accepts Proxy Protocol v1 and processes multiple requests per connection. The bundle explicitly marks eap7-undertow builds in Red Hat JBoss EAP 7.3 EUS for RHEL 7 as affected. Several listed HawtIO, Camel, and JBoss EAP 7.4 entries are marked unaffected. The upstream version range is insufficiently clear.

Exploitation context

The bundle does not identify known active exploitation, and the CVE is not listed as KEV. Network reachability and no required privileges increase theoretical accessibility, but successful impact depends on affected Undertow behavior, Proxy Protocol processing, and connection reuse. No reliable exploit prevalence or demonstrated data disclosure is provided.

Researcher notes

The narrative suggests stale shared StringBuilder state and possible cross-request leakage, while the supplied CVSS vector rates confidentiality and integrity as none and availability as high. That distinction should be preserved during triage. The affected-product data contains advisory-level package entries unrelated by name to Undertow, so validate the actual Undertow package and product status rather than treating every listed package as the vulnerable component.

Mitigation direction

  • Identify the applicable product stream and consult its referenced Red Hat security advisory.
  • Apply vendor-provided updated packages through supported product repositories and normal change controls.
  • Prioritize internet-facing systems using Undertow Proxy Protocol v1 and persistent connections.
  • If updates are delayed, review vendor guidance for supported configuration-based mitigations.
  • Avoid assuming unrelated packages listed under an advisory are independently vulnerable.

Validation and detection

  • Inventory Undertow and eap7-undertow versions, then compare them with the applicable vendor advisory.
  • Determine whether Proxy Protocol v1 is enabled on exposed listeners.
  • Confirm whether affected listeners permit multiple requests over persistent HTTP connections.
  • Review server logs for proxy-protocol parsing errors and unexplained connection termination.
  • After remediation, test authorized staging traffic for isolation of parser state between sequential requests.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-7885 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
14Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-7885Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorundertowundertow, 0, 2.3.0.Alpha1unaffected
Red HatHawtIO 4.0.0 for Red Hat build of Apache Camel 4undertowunaffected
Red HatRed Hat build of Apache Camel 3.20.7 for Spring Bootundertowunaffected
Red HatRed Hat build of Apache Camel 4.4.2 for Spring Bootundertowunaffected
Red HatRed Hat JBoss Enterprise Application Platform 7See advisoryunaffected
Red HatRed Hat JBoss Enterprise Application Platform 7See advisoryunaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-apache-commons-beanutils, 0:1.11.0-1.redhat_00001.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-hornetq, 0:2.4.11-1.Final_redhat_00001.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jboss-server-migration, 0:1.7.2-19.Final_redhat_00020.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-undertow, 0:2.0.41-5.SP6_redhat_00001.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-wildfly, 0:7.3.15-5.GA_redhat_00003.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-annotations, 0:2.10.4-4.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-core, 0:2.10.4-4.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-databind, 0:2.10.4-6.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-jaxrs-providers, 0:2.10.4-4.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-modules-base, 0:2.10.4-6.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-modules-java8, 0:2.10.4-3.redhat_00008.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jboss-server-migration, 0:1.7.2-20.Final_redhat_00021.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-netty, 0:4.1.63-6.Final_redhat_00004.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-undertow, 0:2.0.41-6.SP7_redhat_00001.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-wildfly, 0:7.3.16-3.GA_redhat_00003.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-undertow, 0:2.2.33-2.SP2_redhat_00001.1.el8eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-wildfly, 0:7.4.18-1.GA_redhat_00003.1.el8eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-undertow, 0:2.2.33-2.SP2_redhat_00001.1.el9eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-wildfly, 0:7.4.18-1.GA_redhat_00003.1.el9eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 on RHEL 7eap7-undertow, 0:2.2.33-2.SP2_redhat_00001.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 7.4 on RHEL 7eap7-wildfly, 0:7.4.18-1.GA_redhat_00003.1.el7eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 8undertow-coreunaffected
Red HatRed Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-amazon-ion-java, 0:1.11.9-2.redhat_00001.1.el8eapaffected
Red HatRed Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-eap-product-conf-parent, 0:800.3.1-2.GA_redhat_00002.1.el8eapaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.