CVE-2022-3212
That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.98%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.98% probability · 60th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-770
- Affected
- axum-core project/axum-core
- Source
- reefs@jfrog.com
References
- https://research.jfrog.com/vulnerabilities/axum-core-dos/Exploit, Third Party Advisory
- https://rustsec.org/advisories/RUSTSEC-2022-0055.htmlExploit, Issue Tracking, Patch, Third Party Advisory
- https://research.jfrog.com/vulnerabilities/axum-core-dos/Exploit, Third Party Advisory
- https://rustsec.org/advisories/RUSTSEC-2022-0055.htmlExploit, Issue Tracking, Patch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.