Integration Camel K vulnerabilities
8 known vulnerabilities in Integration Camel K from Red Hat. 8 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
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
RHINT Camel-K-1.10.1: Improper Limitation of a Pathname to a Restricted Directory
A flaw was found in codeplex-codehaus. A directory traversal attack (also known as path traversal) aims to access files and directories stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and their variations or by us
- 8.1 High severity
Openshift Serverless 1 on RHEL 8: Incorrect Authorization
A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy alt
- 7.5 High severity
EAP 7.4.10 release: Loop with Unreachable Exit Condition
A flaw was found in undertow. This issue makes achieving a denial of service possible due to an unexpected handshake status updated in SslConduit, where the loop never terminates.
- 7.5 High severity
undertow: Server-Side Request Forgery
The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.
- 7.5 High severity
undertow: Uncontrolled Resource Consumption
A flaw was found in Undertow. A potential security issue in flow control handling by the browser over HTTP/2 may cause overhead or a denial of service in the server. This flaw exists because of an incomplete fix for CVE-2021-3629.
- 7.5 High severity
xnio: Allocation of Resources Without Limits or Throttling
A flaw was found in XNIO, specifically in the notifyReadClosed method. The issue revealed this method was logging a message to another expected end. This flaw allows an attacker to send flawed requests to a server, possibly causing log contention-related perfo
- 7.5 High severity
Undertow: Uncontrolled Resource Consumption
When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front