{"id":"CVE-2022-3212","state":"PUBLISHED","title":"DoS in axum-core due to missing request size limit","description":"<bytes::Bytes as axum_core::extract::FromRequest>::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","publishedAt":"2022-09-14T16:05:09.000Z","updatedAt":"2024-08-03T01:00:10.862Z","severity":{"score":7.5,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"JFROG"},"assigner":"JFROG","products":["tokio-rs axum-core"],"affected":[{"vendor":"tokio-rs","product":"axum-core","versions":[{"version":"0.3.0-rc.1","status":"affected"},{"version":"unspecified","status":"affected","lessThan":"0.2.8","versionType":"custom"}]}],"references":["https://research.jfrog.com/vulnerabilities/axum-core-dos/","https://rustsec.org/advisories/RUSTSEC-2022-0055.html"],"weaknesses":["CWE-770"],"ingestedAt":"2026-10-29T19:50:32.060Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2022/3xxx/CVE-2022-3212.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2022-3212","state":"PUBLISHED","datePublished":"2022-09-14T16:05:09.000Z","dateUpdated":"2024-08-03T01:00:10.862Z","assignerShortName":"JFROG","assignerOrgId":"48a46f29-ae42-4e1d-90dd-c1676c1e5e6d","dateReserved":"2022-09-14T00:00:00.000Z"},"containers":{"cna":{"title":"DoS in axum-core due to missing request size limit","descriptions":[{"lang":"en","value":"<bytes::Bytes as axum_core::extract::FromRequest>::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"}],"affected":[{"vendor":"tokio-rs","product":"axum-core","versions":[{"version":"0.3.0-rc.1","status":"affected"},{"version":"unspecified","status":"affected","lessThan":"0.2.8","versionType":"custom"}]}],"references":[{"url":"https://research.jfrog.com/vulnerabilities/axum-core-dos/","tags":["x_refsource_MISC"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2022-0055.html","tags":["x_refsource_MISC"]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-770","description":"CWE-770 Allocation of Resources Without Limits or Throttling","lang":"en","type":"CWE"}]}],"providerMetadata":{"shortName":"JFROG","dateUpdated":"2022-09-14T16:05:09.000Z","orgId":"48a46f29-ae42-4e1d-90dd-c1676c1e5e6d"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"security@jfrog.com","ID":"CVE-2022-3212","STATE":"PUBLIC","TITLE":"DoS in axum-core due to missing request size limit"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"axum-core","version":{"version_data":[{"platform":"","version_affected":"<","version_name":"","version_value":"0.2.8"},{"platform":"","version_affected":"=","version_name":"","version_value":"0.3.0-rc.1"}]}}]},"vendor_name":"tokio-rs"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"<bytes::Bytes as axum_core::extract::FromRequest>::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"}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-770 Allocation of Resources Without Limits or Throttling"}]}]},"references":{"reference_data":[{"name":"https://research.jfrog.com/vulnerabilities/axum-core-dos/","refsource":"MISC","url":"https://research.jfrog.com/vulnerabilities/axum-core-dos/"},{"name":"https://rustsec.org/advisories/RUSTSEC-2022-0055.html","refsource":"MISC","url":"https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}]}}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://research.jfrog.com/vulnerabilities/axum-core-dos/","tags":["x_refsource_MISC","x_transferred"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2022-0055.html","tags":["x_refsource_MISC","x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-03T01:00:10.862Z"}}]}}}