Search for packages
| purl | pkg:pypi/mitmproxy@0.14.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-8xbk-3z3r-nkfh
Aliases: CVE-2022-24766 GHSA-gcx2-gvj7-pxv3 PYSEC-2022-170 |
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. |
Affected by 3 other vulnerabilities. |
|
VCID-957h-4a8b-67dy
Aliases: CVE-2025-23217 GHSA-wg33-5h85-7q5p |
Mitmweb API Authentication Bypass Using Proxy Server 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](https://en.wikipedia.org/wiki/Server-side_request_forgery)-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. |
Affected by 2 other vulnerabilities. |
|
VCID-f126-n8nd-jfgs
Aliases: CVE-2021-39214 GHSA-22gh-3r9q-xf38 PYSEC-2021-328 |
url request injection |
Affected by 4 other vulnerabilities. |
|
VCID-m2dr-awrx-nbbe
Aliases: GHSA-63cx-g855-hvv4 |
mitmproxy binaries embed a vulnerable python-hyper/h2 dependency mitmproxy 12.1.1 and below embed python-hyper/h2 ≤ v4.2.0, which has a gap in its HTTP/2 header validation. This enables request smuggling attacks when mitmproxy is in a configuration where it translates HTTP/2 to HTTP/1. For example, this affects reverse proxies to `http://` backends. It does not affect mitmproxy's regular mode. All users are encouraged to upgrade to mitmproxy 12.1.2, which includes a fixed version of h2. More details about the vulnerability itself can be found at https://github.com/python-hyper/h2/security/advisories/GHSA-847f-9342-265h. |
Affected by 1 other vulnerability. |
|
VCID-pddc-5c8v-qqbs
Aliases: CVE-2018-14505 GHSA-6m53-c78q-7qmg PYSEC-2018-56 |
mitmweb in mitmproxy v4.0.3 allows DNS Rebinding attacks, related to tools/web/app.py. |
Affected by 5 other vulnerabilities. |
|
VCID-qgvt-wb92-9kbw
Aliases: CVE-2026-40606 GHSA-527g-3w9m-29hv PYSEC-2026-92 |
mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying the LDAP server. This allows a malicious client to bypass authentication. Only mitmproxy instances using the proxyauth option with LDAP are affected. This option is not enabled by default. The vulnerability has been fixed in mitmproxy 12.2.2 and above. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||