mitmproxy
Affected
- introduced
0, fixed7.0.3(ecosystem)
Fixed versions
7.0.3
Fix
- Fixed version
7.0.3pip install --upgrade mitmproxy==7.0.3
Advisory
Also known as: CVE-2021-39214, PYSEC-2021-328
Lacking Protection against HTTP Request Smuggling in mitmproxy
Impact
In mitmproxy 7.0.2 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 7.0.3 and above.
Acknowledgements
We thank João Sobral (@chinchila) for responsibly disclosing this vulnerability to the mitmproxy team.
Timeline
Critical Basis: The source's own band: CRITICAL
0, fixed 7.0.3 (ecosystem)7.0.3
7.0.3pip install --upgrade mitmproxy==7.0.3Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0