cve.bz

CVE-2020-5236 agendaless waitress: Uncontrolled Resource Consumption

6.5 mediumEPSS 2.4%Fix available

Medium (6.5) in agendaless waitress. EPSS 2.4% estimated probability of exploitation activity in the next 30 days. Fixed in waitress 1.4.3.

On this page
Waitress version 1.4.2 allows a DOS attack When waitress receives a header that contains invalid characters. When a header like "Bad-header: xxxxxxxxxxxxxxx\x10" is received, it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions. This allows an attacker to send a single request with an invalid header and take the service offline. 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. 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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
2.4% (unchanged from 2.4% a week ago; 2.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-5236 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-5236?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-5236?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-5236 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
agendaless:waitress1.4.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-73m2-3pwg-5fgcPyPIwaitress>=1.4.2 <1.4.31.4.3
PYSEC-2020-155PyPIwaitress<1.4.31.4.3

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

* OpenShift Container Platform 4 uses an earlier version of python-waitress which is not affected by this vulnerability.

* Red Hat Quay uses an earlier version of python-waitress which is not affected by this vulnerability.

* Red Hat OpenStack Platform 15 and 16 ship but do not use the flawed version of python-waitress. The impact for these products is therefore rated as having a security impact of Low. (Earlier versions of RHOSP do not ship the flawed code.)

* This issue did not affect Red Hat Ceph Storage 3 and 4 as the vulnerable code is not present in the shipped version of python-waitress.

ProductPackageStateAdvisory
Red Hat Ceph Storage 3python-waitressNot affected
Red Hat Ceph Storage 4python-waitressNot affected
Red Hat OpenShift Container Platform 4python-waitressNot affected
Red Hat OpenStack Platform 13 (Queens)python-waitressNot affected
Red Hat OpenStack Platform 15 (Stein)python-waitressOut of support scope
Red Hat OpenStack Platform 16 (Train)python-waitressFix deferred
Red Hat Quay 3python-waitressNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-5236.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON