CVE-2022-3212
No exploitation reported by the sources we read.
- Published2022-09-14
- Fixed in0.3.0-rc.2 · 0.2.8
- WeaknessCWE-770
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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
Timeline
dates in UTC- 2022-09-1416:15CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.3 | ≥ 0.3.0-rc.1, < 0.3.0-rc.2 | 0.3.0-rc.2 | OSV |
| 0.2 | < 0.2.8 | 0.2.8 | NVD · OSV |
| 0.x | ≥ 0.0.0-0, < 0.2.8 | 0.2.8 | OSV |
| 0.3 | = 0.3.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Axum-core project axum-core to 0.3.0-rc.2 · 0.2.8
Advisories and patches
- rustsec.orgPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.17.5known since 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- CNAweakness (CWE)CWE-770known since 2026-10-23
- NVDweakness (CWE)CWE-770read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2022-09-15
Identifiers
- EUVD-2022-6873same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-m77f-652q-wwp4same flawGitHub Advisory Database · CC-BY-4.0
- RUSTSEC-2022-0055same flawRustSec · CC0-1.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2022-09-14
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-m77f-652q-wwp4
Frequently asked questions
What is CVE-2022-3212?
Is CVE-2022-3212 actively exploited?
What is the CVSS score for CVE-2022-3212?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-m77f-652q-wwp4
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served