CVE-2022-3212
Last modified
CVE-2022-3212 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. <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. EPSS estimates a 0.82% chance of exploitation in the next 30 days.
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
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Axum-Core Project | Axum-Core | < 0.2.8 | — |
| Axum-Core Project | Axum-Core | 0.3.0 | Rc1 |
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
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-3212?
How severe is CVE-2022-3212?
How do I fix CVE-2022-3212?
Are you affected by CVE-2022-3212?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST