Resource exhaustion in Axum-Core Project
CVE-2022-3212
<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
EPSS: 0.009 (54.5th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Affected products
- Axum-core_project Axum-core — versions 0.3.0
- Tokio-rs Axum-core — versions 0.3.0-rc.1, unspecified
Weakness classification (CWE)
Public proof-of-concept exploits
References
- reefs@jfrog.com (Exploit, Third Party Advisory, x_refsource_MISC)
- reefs@jfrog.com (Exploit, Patch, Third Party Advisory, x_refsource_MISC, Issue Tracking)
Frequently asked questions
- What is CVE-2022-3212?
- CVE-2022-3212 is a high-severity vulnerability in Axum-Core Project, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 7.5/10. Published 2022-09-14.
- How severe is CVE-2022-3212?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2022-3212 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.