Red Hat Integration Camel K 1 vulnerabilities
12 known vulnerabilities in Red Hat Integration Camel K 1 from Red Hat. 12 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.5 High severity
A flaw was found in Undertow. Servlets using a method that calls…
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
- 7.5 High severity
A flaw was found in Undertow that can cause remote denial of service attacks.
A flaw was found in Undertow that can cause remote denial of service attacks. When the server uses the FormEncodedDataDefinition.doParse(StreamSourceChannel) method to parse large form data encoding with application/x-www-form-urlencoded, the method will cause
- 7.5 High severity
Red Hat build of Apache Camel 4.8.5 for Spring…: Improperly Controlled Sequential Memory Allocation
A flaw was found in Smallrye, where smallrye-fault-tolerance is vulnerable to an out-of-memory (OOM) issue. This vulnerability is externally triggered when calling the metrics URI. Every call creates a new object within meterMap and may lead to a denial of ser
- 8.1 High severity
Red Hat JBoss Enterprise Application Platform…: Improper Restriction of Excessive Authentication Attempts
A flaw was found in Wildfly Elytron integration. The component does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks via CLI.
- 7.4 High severity
Cryostat 4 on RHEL 9: Inconsistent Interpretation of HTTP Requests
A flaw was found in Quarkus-HTTP, 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
- 7.5 High severity
HawtIO 4.0.0 for Red Hat build of Apache Camel 4: Concurrent Execution using Shared Resource with Improper Synchronization
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 resu
- 7.5 High severity
Red Hat build of Apache Camel 3.20.7 for…: Uncontrolled Recursion
A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response.
- 7.5 High severity
EAP 8.0.1: Exposure of Data Element to Wrong Session
A vulnerability was found in Undertow, where URL-encoded request paths can be mishandled during concurrent requests on the AJP listener. This issue arises because the same buffer is used to decode the paths for multiple requests simultaneously, leading to inco
- 7.0 High severity
HawtIO 4.0.0 for Red Hat build of Apache Camel 4: Cleartext Storage of Sensitive Information in an Environment Variable
A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application's build, therefore, running the resulting application inherits the values captured at build time. Some local
- 7.5 High severity
Red Hat build of Apache Camel 4.4.0 for Spring…: Uncontrolled Resource Consumption
A flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large can lead to uncontrolled resource management and a possible denial of service (DoS).
- 7.5 High severity
Red Hat build of Apache Camel 4.4.1 for Spring…: Uncontrolled Resource Consumption
A vulnerability was found in Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol. Whenever a malicious user opens and closes a connection with the HTTP port of the server and then closes the connection immediately, the
- 9.8 Critical severity
Red Hat build of Quarkus 2.13.9.Final: Improper Handling of Exceptional Conditions
A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not hap