MediumGHSA-73m2-3pwg-5fgcCVE-2020-5236PYSEC-2020-155

Catastrophic backtracking in regex allows Denial of Service in Waitress

Published 4 Feb 2020 · Updated 10 Sept 2026

Is your project on an affected waitress?

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
>=1.4.2 <1.4.3
Fixed in
1.4.3
Update to the fixed version for your release line, for example:pip install 'waitress>=1.4.3'

Details

Impact

When waitress receives a header that contains invalid characters it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions.

This would allow an attacker to send a single request with an invalid header and take the service offline.

Invalid header example:

Bad-header: xxxxxxxxxxxxxxx\x10

Increasing the number of x's in the header will increase the amount of time Waitress spends in the regular expression engine.

This issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behaviour required by errata associated with RFC7230.

Patches

The regular expression that is used to validate incoming headers has been updated in version 1.4.3, it is recommended that people upgrade to the new version of Waitress as soon as possible.

Workarounds

If you have deployed a reverse proxy in front of Waitress it may already be rejecting requests that include invalid headers.

Thanks

The Pylons Project would like to thank Fil Zembowicz for reaching out and disclosing this vulnerability!

References

Catastrophic backtracking explained: https://www.regular-expressions.info/catastrophic.html

For more information

If you have any questions or comments about this advisory:

  • open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
  • email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)

Is GHSA-73m2-3pwg-5fgc 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 waitress, and gives you the command that fixes it.

More advisories for waitress

  • CriticalCVE-2024-49768Waitress has request processing race condition in HTTP pipelining with invalid first request · 29 Oct 2024
  • HighCVE-2024-49769Waitress vulnerable to DoS leading to high CPU usage/resource exhaustion · 29 Oct 2024
  • HighCVE-2022-31015Uncaught Exception (due to a data race) leads to process termination in Waitress · 2 Jun 2022
  • HighCVE-2022-24761HTTP Request Smuggling in waitress · 18 Mar 2022
  • MediumCVE-2019-16789HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up) · 6 Jan 2020
  • HighGHSA-m5ff-3wj3-8ph4HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress · 26 Dec 2019
All 10 advisories for waitress

References

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