CriticalGHSA-c2jg-hw38-jrqqCVE-2022-24801PYSEC-2022-195

Inconsistent Interpretation of HTTP Requests in twisted.web

Published 4 Apr 2022 · Updated 25 Nov 2024

Is your project on an affected twisted?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<22.4.0
Fixed in
22.4.0
Update to the fixed version for your release line, for example:pip install 'twisted>=22.4.0'

Details

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:

1. The Content-Length header value could have a + or - prefix. 2. Illegal characters were permitted in chunked extensions, such as the LF (\n) character. 3. Chunk lengths, which are expressed in hexadecimal format, could have a prefix of 0x. 4. HTTP headers were stripped of all leading and trailing ASCII whitespace, rather than only space and HTAB (\t).

This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling.

Impact

You may be affected if:

1. You use Twisted Web's HTTP 1.1 server and/or proxy 2. You also pass requests through a different HTTP server and/or proxy

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.

Patches

The issue has been addressed in Twisted 22.4.0rc1 and later.

Workarounds

Other than upgrading Twisted, you could:

  • Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them
  • Filter malformed requests by other means, such as configuration of an upstream proxy

Credits

This issue was initially reported by Zhang Zeyu.

Is GHSA-c2jg-hw38-jrqq in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected twisted, and gives you the command that fixes it.

More advisories for twisted

  • HighGHSA-vpp8-g58w-m8mpTwisted: Unauthenticated Remote Denial of Service in the Twisted HTTP/2 Server via Rapid Stream Reset · 29 Oct 2026
  • LowCVE-2026-83813Twisted: DNS Response Spoofing in twisted.names Due to Missing Source Address Validation · 27 Oct 2026
  • MediumCVE-2026-115774Twisted: Denial of Service in the Twisted IMAP4 Server via a Negative Literal Size in SEARCH · 23 Oct 2026
  • HighCVE-2026-115776Twisted: Unauthenticated Remote Denial of Service in the Twisted IRC Server via an Unbounded Line Buffer · 23 Oct 2026
  • HighCVE-2026-115778Twisted: Unauthenticated Remote Denial of Service in the Twisted conch Telnet Transport via an Unbounded Subnegotiation Buffer · 23 Oct 2026
  • HighCVE-2026-115775Twisted: Unauthenticated Remote Denial of Service in the Twisted words domish XML Element Stream via an Unbounded Element Tree · 23 Oct 2026
All 24 advisories for twisted

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.