CVE-2024-4027: Undertow: outofmemoryerror in httpservletrequestimpl.getparameternames() can cause remote dos attacks
A flaw was found in Undertow. Servlets using a method that calls HttpServletRequestImpl.getParameterNames() can cause an OutOfMemoryError when the client sends a request with large parameter names. This issue can be exploited by an unauthorized user to cause a remote denial-of-service (DoS) attack.
Security readout for executives and security teams
Plain-English summary
CVE-2024-4027 is a remote denial-of-service flaw in Undertow. An unauthenticated client can send requests with very large parameter names, causing memory exhaustion in applications that call parameter-name enumeration. The business impact is service outage, not data theft or code execution.
Executive priority
Treat as high priority for exposed services where downtime has material business impact. This is not currently evidenced as exploited, but unauthenticated remote DoS risk justifies fast inventory, vendor-status confirmation, and maintenance planning.
Technical view
The flaw is in Undertow servlet request parameter handling, specifically HttpServletRequestImpl.getParameterNames(). Large parameter names can trigger OutOfMemoryError. CVSS 3.1 is 7.5 high: network reachable, low complexity, no privileges, no user interaction, availability impact only. CWE-20 is listed.
Likely exposure
Most relevant exposure is Undertow-backed servlet applications and Red Hat products marked affected: Apicurio Registry 2, Fuse 7, Integration Camel K 1, and Process Automation 7. Several listed products have unknown status, so asset-specific verification is required.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The issue is still operationally serious because it is unauthenticated, network reachable, and targets availability through memory exhaustion.
Researcher notes
Avoid assuming all Undertow deployments are affected from the bundle alone. Product statuses vary: some are affected, some unaffected, and several unknown. The provided sources do not name exact fixed versions or a universal mitigation.
Mitigation direction
Inventory Undertow and Red Hat products listed in the CVE/VEX records.
Check Red Hat guidance for affected status, errata, and supported fixed packages.
Prioritize internet-facing or unauthenticated servlet applications for remediation planning.
Apply vendor-supported updates when Red Hat publishes applicable fixes.
Review platform-supported request size and parameter controls before changing production limits.
Validation and detection
Map deployed products against the Red Hat CVE and CSAF VEX status.
Confirm whether applications use Undertow servlet handling or quarkus-undertow.
Identify routes that enumerate request parameter names in servlet request processing.
Review monitoring for OutOfMemoryError events or unexplained availability drops.
Retest after vendor updates using non-destructive availability and regression checks.
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-20: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.