WaratekVRT Sign in

Redhat Integration CVEs

21 CVEs, 2 exploited, 5 protected by Waratek

Reset
More filters (2)
Columns
Vendor redhat✕Product integration✕
Overview 21 matches · 5 protected · 2 exploited · 1 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
21matches 5protected23.8% 2exploited9.5% 1CISA KEV4.8% 2public PoC9.5% 2EPSS ≥ 0.59.5%
Protected by Waratek 5 23.8% Rule in development 0 0.0% Mitigation candidate 1 4.8% No exploit published 15 71.4%
Critical 0 0.0% High 15 71.4% Medium 6 28.6% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 5 23.8% partly blocked 0 0.0% not blocked 16 76.2% not established 0 0.0% unrecorded 0 0.0%
Exploited 2 9.5% Working exploit published 0 0.0% Proof of concept only 1 4.8% Forecast only 0 0.0% No public exploit 18 85.7%
split by peak 7 / quarter
No exploit published: 15Mitigation candidate: 1Protected by Waratek: 5 Medium: 6High: 15 not blocked: 16blocked by ARMR today: 5 No public exploit: 18Proof of concept only: 1Exploited: 2
Q1 211 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 Q2 212 No exploit published2 High1 Medium1 not blocked2 No public exploit2 Q3 211 No exploit published1 Medium1 not blocked1 No public exploit1 Q4 211 Protected by Waratek1 High1 blocked by ARMR today1 Exploited1 Q1 220 Q2 221 No exploit published1 Medium1 not blocked1 No public exploit1 Q3 227 Protected by Waratek1 No exploit published6 High5 Medium2 blocked by ARMR today1 not blocked6 No public exploit7 Q4 220 Q1 231 No exploit published1 High1 not blocked1 No public exploit1 Q2 230 Q3 234 Protected by Waratek2 No exploit published2 High3 Medium1 blocked by ARMR today2 not blocked2 Proof of concept only1 No public exploit3 Q4 231 Mitigation candidate1 High1 not blocked1 Exploited1 Q1 241 No exploit published1 High1 not blocked1 No public exploit1 Q2 240 Q3 241 No exploit published1 High1 not blocked1 No public exploit1
Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24
21 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-7885 High 2024-08-21 No exploit published No public exploit 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.
CVE-2024-1635 High 2024-02-19 No exploit published No public exploit 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 server will end with both memory and open file limits exhausted at some point, depending on the amount of memory available. At HTTP upgrade to remoting, the WriteTimeoutStreamSinkConduit leaks connections if RemotingConnection is closed by Remoting ServerConnectionOpenListener. Because the remoting connection originates in Undertow as part of the HTTP upgrade, there is an external layer to the remoting connection. This connection is unaware of the outermost layer when closing the connection during the connection opening procedure. Hence, the Undertow WriteTimeoutStreamSinkConduit is not notified of the closed connection in this scenario. Because WriteTimeoutStreamSinkConduit creates a timeout task, the whole dependency tree leaks via that task, which is added to XNIO WorkerThread. So, the workerThread points to the Undertow conduit, which contains the connections and causes the leak.
CVE-2023-44487 High 2023-10-10 Mitigation candidate Exploited The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
CVE-2022-4245 Medium 2023-09-25 Protected by Waratek No public exploit A flaw was found in codehaus-plexus. The org.codehaus.plexus.util.xml.XmlWriterUtil#writeComment fails to sanitize comments for a --> sequence. This issue means that text contained in the command string could be interpreted as XML and allow for XML injection.
CVE-2022-4244 High 2023-09-25 Protected by Waratek Proof of concept only 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 using absolute file paths, it may be possible to access arbitrary files and directories stored on the file system, including application source code, configuration, and other critical system files.
CVE-2023-4853 High 2023-09-20 No exploit published No public exploit 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 altogether, resulting in unauthorized endpoint access and possibly a denial of service.
CVE-2023-1108 High 2023-09-14 No exploit published No public exploit 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.
CVE-2022-4492 High 2023-02-23 No exploit published No public exploit 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.
CVE-2022-1278 High 2022-09-13 No exploit published No public exploit A flaw was found in WildFly, where an attacker can see deployment names, endpoints, and any other data the trace payload may contain.
CVE-2022-2764 Medium 2022-09-01 No exploit published No public exploit A flaw was found in Undertow. Denial of service can be achieved as Undertow server waits for the LAST_CHUNK forever for EJB invocations.
CVE-2022-1259 High 2022-08-31 No exploit published No public exploit 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.
CVE-2022-0084 High 2022-08-26 No exploit published No public exploit 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 performance concerns or an unwanted disk fill-up.
CVE-2021-4178 Medium 2022-08-24 Protected by Waratek No public exploit A arbitrary code execution flaw was found in the Fabric 8 Kubernetes client affecting versions 5.0.0-beta-1 and above. Due to an improperly configured YAML parsing, this will allow a local and privileged attacker to supply malicious YAML.
CVE-2021-3690 High 2022-08-23 No exploit published No public exploit A flaw was found in Undertow. A buffer leak on the incoming WebSocket PONG message may lead to memory exhaustion. This flaw allows an attacker to cause a denial of service. The highest threat from this vulnerability is availability.
CVE-2022-2053 High 2022-08-05 No exploit published No public exploit 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-end proxy marking the backend worker (application server) as an error state and not forward requests to the worker for a while. In mod_cluster, this continues until the next STATUS request (10 seconds intervals) from the application server updates the server state. So, in the worst case, it can result in "All workers are in error state" and mod_cluster responds "503 Service Unavailable" for a while (up to 10 seconds). In mod_proxy_balancer, it does not forward requests to the worker until the "retry" timeout passes. However, luckily, mod_proxy_balancer has "forcerecovery" setting (On by default; this parameter can force the immediate recovery of all workers without considering the retry parameter of the workers if all workers of a balancer are in error state.). So, unlike mod_cluster, mod_proxy_balancer does not result in responding "503 Service Unavailable". An attacker could use this behavior to send a malicious request and trigger server errors, resulting in DoS (denial of service). This flaw was fixed in Undertow 2.2.19.Final, Undertow 2.3.0.Alpha2.
CVE-2021-3629 Medium 2022-05-24 No exploit published No public exploit A flaw was found in Undertow. A potential security issue in flow control handling by the browser over http/2 may potentially cause overhead or a denial of service in the server. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.40.Final and prior to 2.2.11.Final.
CVE-2021-4104 High 2021-12-14 Protected by Waratek Exploited JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2021-3642 Medium 2021-08-05 No exploit published No public exploit A flaw was found in Wildfly Elytron in versions prior to 1.10.14.Final, prior to 1.15.5.Final and prior to 1.16.1.Final where ScramServer may be susceptible to Timing Attack if enabled. The highest threat of this vulnerability is confidentiality.
CVE-2020-14326 High 2021-06-02 No exploit published No public exploit A vulnerability was found in RESTEasy, where RootNode incorrectly caches routes. This issue results in hash flooding, leading to slower requests with higher CPU time spent searching and adding the entry. This flaw allows an attacker to cause a denial of service.
CVE-2021-3536 Medium 2021-05-20 No exploit published No public exploit A flaw was found in Wildfly in versions before 23.0.2.Final while creating a new role in domain mode via the admin console, it is possible to add a payload in the name field, leading to XSS. This affects Confidentiality and Integrity.
CVE-2021-20218 High 2021-03-16 Protected by Waratek No public exploit A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after. This flaw allows a malicious pod/container to cause applications using the fabric8 kubernetes-client `copy` command to extract files outside the working path. The highest threat from this vulnerability is to integrity and system availability. This has been fixed in kubernetes-client-4.13.2 kubernetes-client-5.0.2 kubernetes-client-4.11.2 kubernetes-client-4.7.2