HTTP Request Smuggling in goliath
High severity
GitHub Reviewed
Published
May 24, 2021
to the GitHub Advisory Database
•
Updated Jan 25, 2023
Description
Published by the National Vulnerability Database
Jun 10, 2020
Reviewed
May 13, 2021
Published to the GitHub Advisory Database
May 24, 2021
Last updated
Jan 25, 2023
goliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.
References