Description
Netty netty-tcnative before 2.0.84.Final contains an SNI hostname spoofing vulnerability that allows remote unauthenticated clients to alter hostnames via JNI NewStringUTF decoding. Attackers can send overlong encodings like 0xC0 0x80 in the ClientHello server_name to confuse SNI-based certificate selection, access decisions, and logging.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
netty netty-tcnative
Default version status: unaffected
0 to < 2.0.84.Finalaffected
pkg:maven/io.netty/netty-tcnativenetty netty-tcnative-boringssl-static
Default version status: unaffected
0 to < 2.0.84.Finalaffected
pkg:maven/io.netty/netty-tcnative-boringssl-staticReferences
- https://github.com/netty/netty-tcnative/security/advisories/GHSA-2784-hxmm-4hgf ↗
- https://github.com/netty/netty-tcnative/commit/a879c85b9776cf478aada3ca69e60b8c0a99ed38 ↗
- https://github.com/netty/netty-tcnative/blob/netty-tcnative-parent-2.0.83.Final/openssl-dynamic/src/main/c/sslcontext.c#L2608 ↗
- https://github.com/netty/netty-tcnative/releases/tag/netty-tcnative-parent-2.0.84.Final ↗
- https://github.com/netty/netty-tcnative ↗
- https://www.vulncheck.com/advisories/netty-netty-tcnative-before-2.0.84-final-sni-hostname-spoofing-via-modified-utf-8-decoding ↗