hshivhare67 / Jetty_v9.4.31_CVE-2023-26049

Other
0 stars 0 forks source link

CVE-2023-34462 (Medium) detected in netty-handler-4.1.3.Final.jar, netty-handler-4.1.28.Final.jar - autoclosed #123

Closed mend-bolt-for-github[bot] closed 9 months ago

mend-bolt-for-github[bot] commented 9 months ago

CVE-2023-34462 - Medium Severity Vulnerability

Vulnerable Libraries - netty-handler-4.1.3.Final.jar, netty-handler-4.1.28.Final.jar

netty-handler-4.1.3.Final.jar

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers and clients.

Library home page: http://netty.io/

Path to dependency file: /tests/test-sessions/test-gcloud-sessions/pom.xml

Path to vulnerable library: /tests/test-sessions/test-gcloud-sessions/pom.xml,/jetty-gcloud/jetty-gcloud-session-manager/pom.xml

Dependency Hierarchy: - google-cloud-datastore-1.0.0.jar (Root Library) - datastore-v1-protos-1.3.0.jar - grpc-google-common-protos-0.1.0.jar - grpc-all-1.0.1.jar - grpc-netty-1.0.1.jar - netty-codec-http2-4.1.3.Final.jar - :x: **netty-handler-4.1.3.Final.jar** (Vulnerable Library)

netty-handler-4.1.28.Final.jar

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers and clients.

Library home page: http://netty.io/

Path to dependency file: /jetty-infinispan/infinispan-remote-query/pom.xml

Path to vulnerable library: /jetty-infinispan/infinispan-remote-query/pom.xml,/tests/test-sessions/test-infinispan-sessions/pom.xml

Dependency Hierarchy: - infinispan-client-hotrod-9.4.8.Final.jar (Root Library) - :x: **netty-handler-4.1.28.Final.jar** (Vulnerable Library)

Found in HEAD commit: 58f30216af0fcc8c8d4ee04369790afc5494c144

Found in base branch: main

Vulnerability Details

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The `SniHandler` can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the `SniHandler` to allocate 16MB of heap. The `SniHandler` class is a handler that waits for the TLS handshake to configure a `SslHandler` according to the indicated server name by the `ClientHello` record. For this matter it allocates a `ByteBuf` using the value defined in the `ClientHello` record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the `SslClientHelloHandler`. This vulnerability has been fixed in version 4.1.94.Final.

Publish Date: 2023-06-22

URL: CVE-2023-34462

CVSS 3 Score Details (6.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-6mjq-h674-j845

Release Date: 2023-06-22

Fix Resolution (io.netty:netty-handler): 4.1.94.Final

Direct dependency fix Resolution (com.google.cloud:google-cloud-datastore): 1.13.0

Fix Resolution (io.netty:netty-handler): 4.1.94.Final

Direct dependency fix Resolution (org.infinispan:infinispan-client-hotrod): 9.4.12.Final


Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 9 months ago

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #125

mend-bolt-for-github[bot] commented 9 months ago

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #125

mend-bolt-for-github[bot] commented 9 months ago

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #125