Skip to content

HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)

High severity GitHub Reviewed Published Jan 2, 2020 in Pylons/waitress • Updated Sep 5, 2023

Package

pip waitress (pip)

Affected versions

< 1.4.2

Patched versions

1.4.2

Description

Impact

The patches introduced to fix GHSA-m5ff-3wj3-8ph4 were not complete and still would allow an attacker to smuggle requests/split a HTTP request with invalid data.

This updates the existing CVE with ID: CVE-2019-16789

Patches

Waitress version 1.4.2 has been updated to now validate HTTP headers better to avoid the issue, completely fixing all known issues with whitespace.

Workarounds

There are no work-arounds, upgrading to Waitress 1.4.2 is highly recommended.

References

See GHSA-m5ff-3wj3-8ph4 for more information on the security issue.

For more information

If you have any questions or comments about this advisory:

References

Published by the National Vulnerability Database Dec 26, 2019
@digitalresistor digitalresistor published to Pylons/waitress Jan 2, 2020
Reviewed Jan 6, 2020
Published to the GitHub Advisory Database Jan 6, 2020
Last updated Sep 5, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N

EPSS score

0.243%
(65th percentile)

Weaknesses

CVE ID

CVE-2019-16789

GHSA ID

GHSA-968f-66r5-5v74

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.