Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2019-16792

Vulnerability in waitress (CVE-2019-16792)

Summary

Vulnerability in waitress (CVE-2019-16792). Data can be tampered with by attackers. Mitigation: upgrade to 1.4.0 or later.

Original description

The description as published by the source.

Impact

Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally.

So a request with:

Content-Length: 10
Content-Length: 10

would get transformed to:

Content-Length: 10, 10

Which would Waitress would then internally set to Content-Lenght: 0.

Waitress would then treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining.

Patches

This issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.

The Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.

Workarounds

Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).

Issues/more security issues:

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2019-16792 has been found in waitress.
Data can be tampered with by attackers.
What to do: upgrade waitress to 1.4.0 or later.
If unsure, ask your IT team or search "waitress CVE-2019-16792" on the vendor's site.

CVE-2019-16792 (waitress) — CWE-444
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4.0 — apply immediately
Workaround: Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-444) exists in waitress.

📍 Affected scope

Check the vendor advisory for the affected versions of waitress.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 1.4.0.

🛡️ Workaround

Workaround: Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'waitress' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'waitress' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で waitress を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this.

    パッチが適用されるまでの応急処置として、Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade waitress to 1.4.0

    ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI waitress
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details