GHSA-f256-j965-7f32

Possible request smuggling in HTTP/2 due missing validation of content-length

En bref

Publiée
Mise à jour
CVE
CVE-2021-21409
CVSS_V3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Description

### Impact The content-length header is not correctly validated if the request only use a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1 This is a followup of https://github.com/netty/netty/security/advisories/GHSA-wm47-8v5p-wjpj which did miss to fix this one case. ### Patches This was fixed as part of 4.1.61.Final ### Workarounds Validation can be done by the user before proxy the request by validating the header.

Paquets affectés

PaquetVersions
Maven · io.netty:netty-codec-http2introduced 4.0.0, fixed 4.1.61.Final
Maven · org.jboss.netty:nettyintroduced 0
Maven · io.netty:nettyintroduced 0

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database