{"answers":{"affected":"3 open source packages ship an affected version, including mitmproxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24766 in the wild and no public exploit code.","fix":"Upgrade mitmproxy to 8.0.0 or later.","what":"CVE-2022-24766 is a critical vulnerability in mitmproxy, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24766 and fix it if it is affected.\n\nWhat it is: CVE-2022-24766 is a critical vulnerability in mitmproxy, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24766 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mitmproxy (PyPI): affected all versions; fixed in 8.0.0\n- mitmproxy (PyPI): affected all versions; fixed in 8.0.0\n- mitmproxy (PyPI): affected all versions; fixed in 8.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-24766/ (Markdown: https://insights.sbomify.com/CVE-2022-24766/index.md)","id":"CVE-2022-24766","markdown":"https://insights.sbomify.com/CVE-2022-24766/index.md","name":"CVE-2022-24766","record":{"aliases":["DEBIAN-CVE-2022-24766","GHSA-gcx2-gvj7-pxv3","PYSEC-2022-170","UBUNTU-CVE-2022-24766","openSUSE-SU-2024:11956-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SSL/TLS intercepting proxy","requires_auth":"none","summary":"Attackers can smuggle HTTP requests through mitmproxy, bypassing custom access controls and sanitization implemented in event hooks.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mitmproxy","vendor":"mitmproxy"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient Protection against HTTP Request Smuggling in mitmproxy","id":"CVE-2022-24766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2022"},"n_packages":3,"n_references":3,"next":{"headline":"Other in Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)","id":"CVE-2022-24767"},"packages":[{"ecosystem":"PyPI","fixed":["8.0.0"],"introduced":["0"],"last_affected":[],"package":"mitmproxy","purl":null,"source":"GHSA-gcx2-gvj7-pxv3"},{"ecosystem":"PyPI","fixed":["8.0.0"],"introduced":["0"],"last_affected":[],"package":"mitmproxy","purl":"pkg:pypi/mitmproxy","source":"GHSA-gcx2-gvj7-pxv3"},{"ecosystem":"PyPI","fixed":["8.0.0"],"introduced":["0"],"last_affected":[],"package":"mitmproxy","purl":"pkg:pypi/mitmproxy","source":"PYSEC-2022-170"}],"prev":{"headline":"Uncontrolled search for the Git directory in Git for Windows","id":"CVE-2022-24765"},"products":["mitmproxy"],"published":"2022-03-21","related":[{"cvss_score":8.8,"headline":"Mitmweb in mitmproxy allows DNS Rebinding attacks","id":"CVE-2018-14505","kev_date_added":null,"published":"2018-07-22"},{"cvss_score":8.1,"headline":"Lacking Protection against HTTP Request Smuggling in mitmproxy","id":"CVE-2021-39214","kev_date_added":null,"published":"2021-09-16"},{"cvss_score":4.8,"headline":"ProxyAuth Addon LDAP Injection in mitmproxy","id":"CVE-2026-40606","kev_date_added":null,"published":"2026-04-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["mitmproxy"]},"summary":"Attackers can smuggle HTTP requests through mitmproxy, bypassing custom access controls and sanitization implemented in event hooks.","url":"https://insights.sbomify.com/CVE-2022-24766/"}