io.netty:netty-codec-http2 vulnerabilities
- Registry
- Maven
- Latest
- 4.2.21.Final
11 known advisories
The latest version, 4.2.21.Final, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http2 -DdepVersion=4.2.21.Final -DforceVersion=trueIs your project on an affected io.netty:netty-codec-http2?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for io.netty:netty-codec-http2
Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memory leak / OOM DoS)
- Affected
- >=4.2.0 <4.2.16.Final · >=4.1.0.Final <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty: [codec-http2] Lack of Host Header Deduplication in HTTP/2→HTTP/1.x Translation Leads to Request Routing Bypass
- Affected
- >=4.2.0.Final <4.2.16.Final · <4.1.136.Final
- Fixed in
- 4.1.136.Final, 4.2.16.Final
Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
netty-codec-http2: ByteBuf Reference-Count Leak in DelegatingDecompressorFrameListener Leads to Memory Exhaustion
- Affected
- <4.1.135.Final · >=4.2.0.Alpha1 <4.2.15.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced
- Affected
- >=4.2.0.Final <4.2.15.Final · <4.1.135.Final
- Fixed in
- 4.1.135.Final, 4.2.15.Final
Netty: HttpContentDecompressor maxAllocation bypass when Content-Encoding set to br/zstd/snappy leads to decompression bomb DoS
- Affected
- >=4.2.0.Alpha1 <4.2.13.Final · <4.1.133.Final
- Fixed in
- 4.1.133.Final, 4.2.13.Final
Netty HTTP/2 CONTINUATION Frame Flood DoS via Zero-Byte Frame Bypass
- Affected
- <4.1.132.Final · >=4.2.0.Alpha1 <4.2.11.Final
- Fixed in
- 4.1.132.Final, 4.2.11.Final
Netty affected by MadeYouReset HTTP/2 DDoS vulnerability
- Affected
- >=4.2.0.Alpha1 <4.2.4.Final · <4.1.124.Final
- Fixed in
- 4.1.124.Final, 4.2.4.Final
io.netty:netty-codec-http2 vulnerable to HTTP/2 Rapid Reset Attack
- Affected
- <4.1.100.Final
- Fixed in
- 4.1.100.Final
Possible request smuggling in HTTP/2 due missing validation of content-length
- Affected
- >=4.0.0 <4.1.61.Final
- Fixed in
- 4.1.61.Final
Possible request smuggling in HTTP/2 due missing validation
- Affected
- >=4.0.0 <4.1.60.Final
- Fixed in
- 4.1.60.Final
Is your io.netty:netty-codec-http2 version vulnerable?
Which of your client projects still run an old io.netty:netty-codec-http2?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.