CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
PARTIAL
AV:N/AC:M/Au:N/C:N/I:N/A:P
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
Percentile
56.7%
Waitress may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed.
This issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket, instead it is always delegated to the main thread.
There is no work-around, however users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.
If you have any questions or comments about this advisory:
Vendor | Product | Version | CPE |
---|---|---|---|
agendaless | waitress | * | cpe:2.3:a:agendaless:waitress:*:*:*:*:*:*:*:* |
github.com/advisories/GHSA-f5x9-8jwc-25rw
github.com/Pylons/waitress/commit/4f6789b035610e0552738cdc4b35ca809a592d48
github.com/Pylons/waitress/issues/374
github.com/Pylons/waitress/pull/377
github.com/Pylons/waitress/security/advisories/GHSA-f5x9-8jwc-25rw
github.com/pypa/advisory-database/tree/main/vulns/waitress/PYSEC-2022-205.yaml
nvd.nist.gov/vuln/detail/CVE-2022-31015
CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
PARTIAL
AV:N/AC:M/Au:N/C:N/I:N/A:P
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
Percentile
56.7%