CVE-2022-3212

DoS in axum-core due to missing request size limit

HIGH
7.5
CVSS Score
Published: September 14, 2022 at 04:05 PM UTC
Updated: June 17, 2026 at 04:59 AM UTC
2 products affected across 2 vendorsAxum CoreCore Project Axum Core

Using axum-core by tokio-rs?

Get instant alerts when new vulnerabilities affect axum-core - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.2.80.3.0 rc1
Affected range stops below 0.2.8, so it looks safe — our inference, not a vendor statement
v < 0.2.80.3.0-rc.1
Affected range stops below 0.2.8, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_MISCExploitThird Party Advisory
https://research.jfrog.com/vulnerabilities/axum-core-dos/
x_refsource_MISCExploitIssue TrackingPatchThird Party Advisory
https://rustsec.org/advisories/RUSTSEC-2022-0055.html

CVSS

7.5HIGHJFROG
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card