operatorfabric-core
operatorfabric-core copied to clipboard
CVE-2025-24970 (High) detected in netty-handler-4.1.115.Final.jar
CVE-2025-24970 - High Severity Vulnerability
Vulnerable Library - netty-handler-4.1.115.Final.jar
Library home page: https://netty.io/
Path to dependency file: /src/test/api/karate/karateTests.gradle
Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/io.netty/netty-handler/4.1.115.Final/d54dbf68b9d88a98240107758c6b63da5e46e23a/netty-handler-4.1.115.Final.jar
Dependency Hierarchy:
- karate-junit5-1.5.1.jar (Root Library)
- karate-core-1.5.1.jar
- armeria-1.31.3.jar
- netty-handler-proxy-4.1.115.Final.jar
- netty-codec-http-4.1.115.Final.jar
- :x: netty-handler-4.1.115.Final.jar (Vulnerable Library)
- netty-codec-http-4.1.115.Final.jar
- netty-handler-proxy-4.1.115.Final.jar
- armeria-1.31.3.jar
- karate-core-1.5.1.jar
Found in base branch: develop
Vulnerability Details
Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final and prior to version 4.1.118.Final. When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash. Version 4.1.118.Final contains a patch. As workaround its possible to either disable the usage of the native SSLEngine or change the code manually.
Publish Date: 2025-02-10
URL: CVE-2025-24970
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-4g8c-wm8x-jfhw
Release Date: 2025-02-10
Fix Resolution: io.netty:netty-handler:4.1.118.Final
Step up your Open Source Security Game with Mend here
Not affected as we are note using https with netty
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.