CVE-2023-4639
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2023-4639 is a high-severity HTTP Request/Response Smuggling (CWE-444) vulnerability. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-7 (Boundary Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A flaw was found in Undertow that causes incorrect parsing of cookies containing certain value-delimiting characters in incoming HTTP requests. The affected component is the Undertow web server used in Red Hat middleware products. The vulnerability, tracked as CVE-2023-4639 and assigned CWE-444, permits construction of malicious cookie values that can exfiltrate HttpOnly cookies or inject arbitrary additional cookies, resulting in impacts to data confidentiality and integrity. It carries a CVSS 3.1 base score of 7.4.
An unauthenticated remote attacker can exploit the issue over the network by sending crafted requests containing specially formatted cookies. Successful exploitation allows the attacker to read or overwrite sensitive session or authentication cookies without requiring user interaction, potentially leading to unauthorized access or modification of application data.
Red Hat has published multiple advisories (RHSA-2024:1674, RHSA-2024:1675, RHSA-2024:1676, RHSA-2024:1677, and RHSA-2024:2763) that address the flaw through updated Undertow packages. The EPSS score has remained flat at 0.0736 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-3185
Vulnerability Data
A flaw was found in Undertow, which incorrectly parses cookies with certain value-delimiting characters in incoming requests. This issue could allow an attacker to construct a cookie value to exfiltrate HttpOnly cookie values or spoof arbitrary additional cookie values, leading…
more
to unauthorized data access or modification. The main threat from this flaw impacts data confidentiality and integrity.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.1.3V4.2.4V1.5.3V4.1.1
Mitigating Controls (NIST 800-53 r5) AI
Boundary protection at external interfaces can enforce consistent HTTP request/response parsing rules between intermediaries and endpoints.
Validating HTTP inputs at the intermediary prevents malformed messages from being interpreted inconsistently downstream.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.
Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.
Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect HTTP request smuggling vulnerabilities in intermediary components.
Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.
Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.
Secure SDLC practices require threat modeling and testing for HTTP parsing inconsistencies in intermediaries.
Application security requirements can mandate strict HTTP message validation and canonicalization.
Secure architecture principles include consistent protocol handling and defense-in-depth for proxies.