Update dependency io.undertow:undertow-core to v2.3.14.Final [SECURITY] #604
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.20.Final->2.3.14.FinalGitHub Vulnerability Alerts
CVE-2022-4492
The undertow client is not checking the server identity presented by the server certificate in https connections. This should be performed by default in https and in http/2.
CVE-2023-1108
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-2024-1459
A path traversal vulnerability was found in Undertow. This issue may allow a remote attacker to append a specially-crafted sequence to an HTTP request for an application deployed to JBoss EAP, which may permit access to privileged or restricted files and directories.
CVE-2024-1635
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-2024-5971
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\ntermination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.CVE-2024-7885
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-6162
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 incorrect path information being processed. As a result, the server may attempt to access the wrong path, causing errors such as "404 Not Found" or other application failures. This flaw can potentially lead to a denial of service, as legitimate resources become inaccessible due to the path mix-up.
CVE-2024-3653
A vulnerability was found in Undertow. This issue requires enabling the learning-push handler in the server's config, which is disabled by default, leaving the maxAge config in the handler unconfigured. The default is -1, which makes the handler vulnerable. If someone overwrites that config, the server is not subject to the attack. The attacker needs to be able to reach the server with a normal HTTP request.
CVE-2023-1973
A flaw was found in Undertow package. Using the FormAuthenticationMechanism, a malicious user could trigger a Denial of Service by sending crafted requests, leading the server to an OutofMemory error, exhausting the server's memory.
CVE-2023-4639
A flaw was found in Undertow, 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 cookie values, leading to unauthorized data access or modification. The main threat from this flaw impacts data confidentiality and integrity.
Release Notes
undertow-io/undertow (io.undertow:undertow-core)
v2.3.14.FinalCompare Source
Includes CVES: CVE-2024-6162 CVE-2024-27316 CVE-2023-5685
Sub-task
Bug
Component Upgrade
Enhancement
v2.3.13.FinalCompare Source
v2.3.12.FinalCompare Source
v2.3.11.FinalCompare Source
v2.3.10.FinalCompare Source
v2.3.9.FinalCompare Source
v2.3.8.FinalCompare Source
v2.3.7.FinalCompare Source
v2.3.6.FinalCompare Source
v2.3.5.FinalCompare Source
v2.3.4.FinalCompare Source
v2.3.3.FinalCompare Source
v2.3.2.FinalCompare Source
v2.3.1.FinalCompare Source
v2.3.0.FinalCompare Source
v2.2.37.FinalCompare Source
Undertow release 2.2.37.Final
Full list of Issues: see on Jira
Bug
v2.2.36.FinalCompare Source
Includes CVES: CVE-2024-7885
Bug
Enhancement
v2.2.35.Final: v.2.2.35.FinalCompare Source
Release Notes - Undertow - Version 2.2.35.Final
Bug
v2.2.34.FinalCompare Source
Includes CVES: CVE-2024-3653 CVE-2024-5971
Bug
Documentation
Enhancement
v2.2.33.FinalCompare Source
Includes CVES: CVE-2024-6162 CVE-2024-27316 CVE-2023-5685
Sub-task
Bug
Component Upgrade
Enhancement
v2.2.32.FinalCompare Source
v2.2.31.FinalCompare Source
v2.2.30.FinalCompare Source
v2.2.29.FinalCompare Source
v2.2.28.FinalCompare Source
v2.2.27.FinalCompare Source
v2.2.26.FinalCompare Source
v2.2.25.FinalCompare Source
v2.2.24.FinalCompare Source
v2.2.23.FinalCompare Source
v2.2.22.FinalCompare Source
v2.2.21.FinalCompare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.