You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Hello, I may have found a bug in hypercorn's parsing of HTTP requests with duplicate Content-Type header.
RFC 9110 says these:
Although Content-Type is defined as a singleton field, it is sometimes incorrectly generated multiple times, resulting in a combined field value that appears to be a list. Recipients often attempt to handle this error by using the last syntactically valid member of the list, leading to potential interoperability and security issues if different implementations have different error handling behaviors.
Waitress does not reject such requests. For example:
POST / HTTP/1.1\r\n
Host: victim.com\r\n
Content-Type: text/plain\r\n
Content-Type: application/json\r\n
\r\n
Recipients often attempt to handle this error by using the last syntactically valid member of the list, leading to potential interoperability and security issues if different implementations have different error handling behaviors.
If different implementations have different error handling behaviors, there may be potential interoperability and security issues. So I might suggest rejecting such requests.
The text was updated successfully, but these errors were encountered:
Version
84d06b8
Platform
Ubuntu 11.4.0-1ubuntu1~22.04
Description
Hello, I may have found a bug in hypercorn's parsing of HTTP requests with duplicate
Content-Type
header.RFC 9110 says these:
Waitress does not reject such requests. For example:
If different implementations have different error handling behaviors, there may be potential interoperability and security issues. So I might suggest rejecting such requests.
The text was updated successfully, but these errors were encountered: