CVE-2022-3212 json
DoS in axum-core due to missing request size limit
published 4y ago modified 4mo ago also GHSA-m77f-652q-wwp4 , RUSTSEC-2022-0055 , EUVD-2022-6873
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
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
Patch / fix
- crates.io axum-core 0.2.8, 0.3.0-rc.2
- tokio-rs axum-core 0.2.8
- github.com/tokio-rs/axum#1346 pull request
- rustsec.org/advisories/RUSTSEC-2022-0055.html advisory
Is CVE-2022-3212 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2022-0055.html referenced PoC, tagged "exploit" by a source, unverified
- research.jfrog.com https://research.jfrog.com/vulnerabilities/axum-core-dos/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | axum-core | <0.2.8 >=0.3.0-rc.1, <0.3.0-rc.2 >=0.0.0-0, <0.2.8 |
0.2.8 0.3.0-rc.2 |
Affected products
- tokio-rs axum-core
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
rustsec.org
/advisories/RUSTSEC-2022-0055.html
web, exploit, issue-tracking, patch, third-party-advisory, advisory
-
github.com
/tokio-rs/axum/pull/1346
web
-
research.jfrog.com
/vulnerabilities/axum-core-dos/
exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3212
advisory
-
github.com
/tokio-rs/axum
package
-
crates.io
/crates/axum-core
package
Sources
- CVE List CVE-2022-3212
- GitHub Advisory GHSA-m77f-652q-wwp4
- NVD CVE-2022-3212
- OSV RUSTSEC-2022-0055
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.