CVE-2019-16785
Agendaless Waitress vulnerability
Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.
Affected products
Waitress, Communications Cloud Native Core Network Function Cloud Native Environment, Debian Linux, Fedora, Openstack. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Agendaless Waitress runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes · Vendor Advisory
- github.com/Pylons/waitress/commit/8eba394ad75deaf9e5cd15b78a3d16b12e6b0eba · Patch
- www.oracle.com/security-alerts/cpuapr2022.html · Patch
- access.redhat.com/errata/RHSA-2020:0720 · Third Party Advisory
- github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p · Exploit
- lists.debian.org/debian-lts-announce/2022/05/msg00011.html · Third Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/G
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L
- nvd.nist.gov/vuln/detail/CVE-2019-16785
- cve.org/CVERecord?id=CVE-2019-16785
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.