Possible request smuggling in HTTP/2 due missing validation of content-length
Description
Reviewed
Mar 30, 2021
Published to the GitHub Advisory Database
Mar 30, 2021
Published by the National Vulnerability Database
Mar 30, 2021
Last updated
Aug 16, 2023
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 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.
References