The Twisted Web HTTP 1.1 server, located in the twisted.web.http
module, parsed several HTTP request constructs more leniently than permitted by RFC 7230:
+
or -
prefix.\n
) character.0x
.\t
).This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling.
You may be affected if:
The specifics of the other HTTP parser matter. The original report notes that some versions of Apache Traffic Server and HAProxy have been vulnerable in the past. HTTP request smuggling may be a serious concern if you use a proxy to perform request validation or access control.
The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected.
The issue has been addressed in Twisted 22.4.0rc1 and later.
Other than upgrading Twisted, you could:
This issue was initially reported by Zhang Zeyu.
{ "nvd_published_at": "2022-04-04T18:15:00Z", "cwe_ids": [ "CWE-444" ], "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2022-04-04T21:29:41Z" }