Insufficient Protection against HTTP Request Smuggling in mitmproxy

緊急 9.8CVE-2022-24766 · GHSA-gcx2-gvj7-pxv3 · PYSEC-2022-170 · 21/03/2022 公開 · 17/06/2026 更新

要点

CVE-2022-24766 は mitmproxy, mitmproxy (mitmproxy) に影響する深刻度「緊急」 (CVSS 9.8) の脆弱性です。
今後30日間に悪用される確率（EPSS）：1.6%（全脆弱性の 76.3% より高い）。
対処：8.0.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
mitmproxy PyPI	`< 8.0.0`	`8.0.0`
mitmproxy mitmproxy	`≤ 7.0.4`	修正版なし

概要

Impact

In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization.

Unless you use mitmproxy to protect an HTTP/1 service, no action is required.

Patches

The vulnerability has been fixed in mitmproxy 8.0.0 and above.

Acknowledgements

We thank Zeyu Zhang (@zeyu2001) for responsibly disclosing this vulnerability to the mitmproxy team.

Timeline

2022-03-15: Received initial report.
2022-03-15: Verified report and confirmed receipt.
2022-03-16: Shared patch with researcher.
2022-03-16: Received confirmation that patch is working.
2022-03-19: Published patched release and advisory.

NVD の説明

mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.