Resource exhaustion in Axum-Core Project
CVE-2022-3212
- CVSS v3
- 7.5 High
- Public exploits
- None known
- EPSS
- 0.010 · 64.3th percentile
- Published
- 2022-09-14
<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
Published · last modified .
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.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- None
I:N - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.010, 64.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Axum-Core Project — versions 0.3.0
- Tokio-Rs Axum-Core — versions 0.3.0-rc.1, unspecified
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (leoambrus/artefactswithoutCVEonGitHubAdvisoryDatabase). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- research.jfrog.com/vulnerabilities/axum-core-dos/ (Exploit, Third Party Advisory)
- rustsec.org/advisories/RUSTSEC-2022-0055.html (Exploit, Patch, Third Party Advisory, Issue Tracking)