CVE-2022-3212
Summary
| CVE | CVE-2022-3212 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-09-14 16:15:00 UTC |
| Updated | 2022-09-16 19:22:00 UTC |
| 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 |
Risk And Classification
Problem Types: CWE-770
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Axum-core Project | Axum-core | All | All | All | All |
| Application | Axum-core Project | Axum-core | 0.3.0 | rc1 | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| RUSTSEC-2022-0055: axum-core: No default limit put on request bodies › RustSec Advisory Database | CONFIRM | rustsec.org | |
| axum-core missing request size limit DoS | - JFrog Security Research | CONFIRM | research.jfrog.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.