CVE-2023-4586:
Withdrawn Advisory: Netty-handler does not validate host names by default
5.3
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.28545%
CWE
Published
10/4/2023
Updated
11/10/2023
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
io.netty:netty-handler | maven | >= 4.1.0.Final, <= 4.1.99.Final |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from Netty's default SSL/TLS configuration not enabling hostname validation. The critical point of failure is the initialization of the SSLEngine via SslContext.newEngine, which does not set the endpoint identification algorithm to 'HTTPS' in SSLParameters. This omission bypasses certificate hostname validation. The advisory explicitly states that users must manually configure SSLParameters with 'HTTPS' to mitigate this, confirming that the default engine creation logic is the root cause. The function SslContext.newEngine is directly responsible for SSLEngine initialization in Netty, making it the primary vulnerable function.