CVE-2022-3212GHSA-M77F-652Q-WWP4RUSTSEC-2022-0055
DoS in axum-core due to missing request size limit
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.2.8, 0.3.0-rc.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
<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
Timeline
- CVE published
- Record last updated
Affected versions
- tokio-rs axum-core
fixed in 0.2.8
- axum-corecrates.io
fixed in 0.2.8
- axum-corecrates.io
From 0.3.0-rc.1 · fixed in 0.3.0-rc.2
- axum-corecrates.io
From 0.0.0-0 · fixed in 0.2.8; From 0.3.0-rc.1 · fixed in 0.3.0-rc.2