En resumen
- CVE-2022-24766 es una vulnerabilidad CRÍTICO (CVSS 9.8) que afecta a mitmproxy, mitmproxy (mitmproxy).
- Probabilidad de explotación en los próximos 30 días (EPSS): 1.6%, mayor que el 76.3% de las vulnerabilidades.
- Solución: actualizar a 8.0.0 o posterior.
| Package | Affected versions | Patched versions |
|---|
| mitmproxy PyPI | < 8.0.0
| 8.0.0
|
| mitmproxy | ≤ 7.0.4
| No fix yet |
Description
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 description
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free