Vulnerabilities (CVE)

Filtered by vendor Redhat Subscribe
Filtered by product Build Of Apache Camel For Spring Boot
Total 4 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2026-28368 1 Redhat 10 Build Of Apache Camel - Hawtio, Build Of Apache Camel For Spring Boot, Data Grid and 7 more 2026-03-31 N/A 8.7 HIGH
A flaw was found in Undertow. This vulnerability allows a remote attacker to construct specially crafted requests where header names are parsed differently by Undertow compared to upstream proxies. This discrepancy in header interpretation can be exploited to launch request smuggling attacks, potentially bypassing security controls and accessing unauthorized resources.
CVE-2026-28369 1 Redhat 10 Build Of Apache Camel - Hawtio, Build Of Apache Camel For Spring Boot, Data Grid and 7 more 2026-03-31 N/A 8.7 HIGH
A flaw was found in Undertow. When Undertow receives an HTTP request where the first header line starts with one or more spaces, it incorrectly processes the request by stripping these leading spaces. This behavior, which violates HTTP standards, can be exploited by a remote attacker to perform request smuggling. Request smuggling allows an attacker to bypass security mechanisms, access restricted information, or manipulate web caches, potentially leading to unauthorized actions or data exposure.
CVE-2025-9784 1 Redhat 8 Build Of Apache Camel For Spring Boot, Enterprise Linux, Fuse and 5 more 2026-03-18 N/A 7.5 HIGH
A flaw was found in Undertow where malformed client requests can trigger server-side stream resets without triggering abuse counters. This issue, referred to as the "MadeYouReset" attack, allows malicious clients to induce excessive server workload by repeatedly causing server-side stream aborts. While not a protocol bug, this highlights a common implementation weakness that can be exploited to cause a denial of service (DoS).
CVE-2024-7885 1 Redhat 9 Build Of Apache Camel - Hawtio, Build Of Apache Camel For Spring Boot, Build Of Keycloak and 6 more 2026-01-19 N/A 7.5 HIGH
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.