Skip to content

Withdrawn Advisory: undertow: information leakage via HTTP/2 request header reuse

High severity GitHub Reviewed Published Dec 12, 2024 to the GitHub Advisory Database • Updated Jan 16, 2025
Withdrawn This advisory was withdrawn on Jan 16, 2025

Package

maven io.undertow:undertow-core (Maven)

Affected versions

<= 2.3.18.Final

Patched versions

None

Description

Withdrawn Advisory

This advisory has been withdrawn because it was determined to not be a valid vulnerability. This link is maintained to preserve external references. For more information, see https://nvd.nist.gov/vuln/detail/CVE-2024-4109.

Original Description

A flaw was found in Undertow. An HTTP request header value from a previous stream may be incorrectly reused for a request associated with a subsequent stream on the same HTTP/2 connection. This issue can potentially lead to information leakage between requests.

References

Published by the National Vulnerability Database Dec 12, 2024
Published to the GitHub Advisory Database Dec 12, 2024
Reviewed Dec 12, 2024
Withdrawn Jan 16, 2025
Last updated Jan 16, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2024-4109

GHSA ID

GHSA-22c5-cpvr-cfvq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.