{ "data_type": "CVE", "data_format": "MITRE", "data_version": "4.0", "CVE_data_meta": { "ID": "CVE-2022-3212", "ASSIGNER": "security@jfrog.com", "TITLE": "DoS in axum-core due to missing request size limit", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "vendor_name": "tokio-rs", "product": { "product_data": [ { "product_name": "axum-core", "version": { "version_data": [ { "version_name": "", "version_affected": "<", "version_value": "0.2.8", "platform": "" }, { "version_name": "", "version_affected": "=", "version_value": "0.3.0-rc.1", "platform": "" } ] } } ] } } ] } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-770 Allocation of Resources Without Limits or Throttling" } ] } ] }, "description": { "description_data": [ { "lang": "eng", "value": "::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String" } ] }, "references": { "reference_data": [ { "refsource": "MISC", "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/", "name": "https://research.jfrog.com/vulnerabilities/axum-core-dos/" }, { "refsource": "MISC", "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html", "name": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html" } ] }, "impact": { "cvss": { "version": "3.1", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "availabilityImpact": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "baseScore": 7.5, "baseSeverity": "HIGH" } } }