{"api_version":"1","generated_at":"2026-04-22T23:31:50+00:00","cve":"CVE-2022-24766","urls":{"html":"https://cve.report/CVE-2022-24766","api":"https://cve.report/api/cve/CVE-2022-24766.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2022-24766","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-24766"},"summary":{"title":"CVE-2022-24766","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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2022-03-21 19:15:00","updated_at":"2022-03-29 16:49:00"},"problem_types":["CWE-444"],"metrics":[],"references":[{"url":"https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b","name":"https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b","refsource":"MISC","tags":[],"title":"security: reject whitespace in HTTP/1 header names · mitmproxy/mitmproxy@b06fb6d · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://mitmproxy.org/posts/releases/mitmproxy8/","name":"https://mitmproxy.org/posts/releases/mitmproxy8/","refsource":"MISC","tags":[],"title":"Mitmproxy 8","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3","name":"https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3","refsource":"CONFIRM","tags":[],"title":"Insufficient Protection against HTTP Request Smuggling in mitmproxy · Advisory · mitmproxy/mitmproxy · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-24766","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-24766","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2022","cve_id":"24766","vulnerable":"1","versionEndIncluding":"7.0.4","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"mitmproxy","cpe5":"mitmproxy","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2022-24766","qid":"184426","title":"Debian Security Update for mitmproxy (CVE-2022-24766)"},{"cve":"CVE-2022-24766","qid":"690885","title":"Free Berkeley Software Distribution (FreeBSD) Security Update for mitmproxy (ad37a349-ebb7-11ec-b9f7-21427354249d)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2022-24766","STATE":"PUBLIC","TITLE":"Insufficient Protection against HTTP Request Smuggling in mitmproxy"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"mitmproxy","version":{"version_data":[{"version_value":"<= 7.0.4"}]}}]},"vendor_name":"mitmproxy"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')"}]}]},"references":{"reference_data":[{"name":"https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3","refsource":"CONFIRM","url":"https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-gcx2-gvj7-pxv3"},{"name":"https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b","refsource":"MISC","url":"https://github.com/mitmproxy/mitmproxy/commit/b06fb6d157087d526bd02e7aadbe37c56865c71b"},{"name":"https://mitmproxy.org/posts/releases/mitmproxy8/","refsource":"MISC","url":"https://mitmproxy.org/posts/releases/mitmproxy8/"}]},"source":{"advisory":"GHSA-gcx2-gvj7-pxv3","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2022-03-21 19:15:00","lastModifiedDate":"2022-03-29 16:49:00","problem_types":["CWE-444"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL"},"exploitabilityScore":3.9,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":7.5},"severity":"HIGH","exploitabilityScore":10,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mitmproxy:mitmproxy:*:*:*:*:*:*:*:*","versionEndIncluding":"7.0.4","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2022","CveId":"24766","Ordinal":"228256","Title":"CVE-2022-24766","CVE":"CVE-2022-24766","Year":"2022"},"notes":[{"CveYear":"2022","CveId":"24766","Ordinal":"1","NoteData":"** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.","Type":"Description","Title":null}]}}}