CVE-2022-24766 SUSE CVE security@suse.de SUSE Security Team SUSE CVE-2022-24766 Interim 1 2 2022-10-05T23:40:26Z current 2022-04-03T02:01:50Z 2022-10-05T23:40:26Z cve-database/bin/generate-cvrf-cve.pl 2020-12-27T01:00:00Z CVE-2022-24766 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. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). https://www.suse.com/support/security/rating/ SUSE Security Ratings openSUSE Tumbleweed python310-mitmproxy-8.0.0-1.1 python38-mitmproxy-8.0.0-1.1 python39-mitmproxy-8.0.0-1.1 python310-mitmproxy-8.0.0-1.1 as a component of openSUSE Tumbleweed python38-mitmproxy-8.0.0-1.1 as a component of openSUSE Tumbleweed python39-mitmproxy-8.0.0-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:python310-mitmproxy-8.0.0-1.1 openSUSE Tumbleweed:python38-mitmproxy-8.0.0-1.1 openSUSE Tumbleweed:python39-mitmproxy-8.0.0-1.1 important 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H