mitmproxy
Affected
- introduced
0, fixed11.1.2(ecosystem)
Fixed versions
11.1.2
Fix
- Fixed version
11.1.2pip install --upgrade mitmproxy==11.1.2
Advisory
Also known as: CVE-2025-23217, GHSA-wg33-5h85-7q5p
Mitmweb API Authentication Bypass Using Proxy Server
Impact
In mitmweb 11.1.0 and below, a malicious client can use mitmweb's proxy server (bound to *:8080 by default) to access mitmweb's internal API (bound to 127.0.0.1:8081 by default). In other words, while the client cannot access the API directly (good), they can access the API through the proxy (bad). An attacker may be able to escalate this SSRF-style access to remote code execution.
The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. The block_global option, which is enabled by default, blocks connections originating from publicly-routable IP addresses in the proxy. The attacker needs to be in the same local network.
Patches
The vulnerability has been fixed in mitmproxy 11.1.2 and above.
Acknowledgements
We thank Stefan Grönke (@gronke) for reporting this vulnerability as part of a security audit by Radically Open Security. This audit was supported by the NGI0 Entrust fund established by NLnet.
Timeline
Not rated by the source.
0, fixed 11.1.2 (ecosystem)11.1.2
11.1.2pip install --upgrade mitmproxy==11.1.2Fix 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: PyPA Advisory Database · CC BY 4.0