python312-mitmproxy-11.1.2-1.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2025:15824 Final 1 1 2025-02-10T00:00:00Z current 2025-02-10T00:00:00Z 2025-02-10T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z python312-mitmproxy-11.1.2-1.1 on GA media These are all security issues fixed in the python312-mitmproxy-11.1.2-1.1 package on the GA media of openSUSE Tumbleweed. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Tumbleweed-2025-15824 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2022-24766/ SUSE CVE CVE-2022-24766 page https://www.suse.com/security/cve/CVE-2022-3602/ SUSE CVE CVE-2022-3602 page https://www.suse.com/security/cve/CVE-2025-23217/ SUSE CVE CVE-2025-23217 page openSUSE Tumbleweed python312-mitmproxy-11.1.2-1.1 python313-mitmproxy-11.1.2-1.1 python312-mitmproxy-11.1.2-1.1 as a component of openSUSE Tumbleweed python313-mitmproxy-11.1.2-1.1 as a component of openSUSE Tumbleweed 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. CVE-2022-24766 openSUSE Tumbleweed:python312-mitmproxy-11.1.2-1.1 openSUSE Tumbleweed:python313-mitmproxy-11.1.2-1.1 moderate 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2022-24766.html CVE-2022-24766 https://bugzilla.suse.com/1197381 SUSE Bug 1197381 A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler. Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). CVE-2022-3602 openSUSE Tumbleweed:python312-mitmproxy-11.1.2-1.1 openSUSE Tumbleweed:python313-mitmproxy-11.1.2-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2022-3602.html CVE-2022-3602 https://bugzilla.suse.com/1204714 SUSE Bug 1204714 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 mitmweb 11.1.1 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 cannot access the API directly, they can access the API through the proxy. 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. This vulnerability has been fixed in mitmproxy 11.1.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE-2025-23217 openSUSE Tumbleweed:python312-mitmproxy-11.1.2-1.1 openSUSE Tumbleweed:python313-mitmproxy-11.1.2-1.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2025-23217.html CVE-2025-23217 https://bugzilla.suse.com/1236890 SUSE Bug 1236890