Loading...
Skip to main content
GeekWala

CVE-2022-3212 — Vulnerability in axum-core — CVE Details

HIGH

axum-core has no default limit put on request bodies

Published September 15, 2022Updated November 8, 2023Source: osv

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` The fix is also in `axum-core` `0.3.0.rc.2` but `0.3.0.rc.1` _is_ vulnerable. Because `axum` depends on `axum-core` it is vulnerable as well. The vulnerable versions of `axum` are `<= 0.5.15` and `0.6.0.rc.1`. `axum` `>= 0.5.16` and `>= 0.6.0.rc.2` does have the fix and are not vulnerable. The patched versions will set a 2 MB limit by default.

Advisory Timeline

  • First published September 15, 2022 (1488 days ago).
  • Last revised November 8, 2023 — 419 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Cargo
Update axum-core to 0.3.0-rc.2 or later
cargo update -p axum-core --precise 0.3.0-rc.2
Cargo
Update axum-core to 0.2.8 or later
cargo update -p axum-core --precise 0.2.8

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: crates.io (1).

PackageEcosystemAffectedFixed In
axum-core
crates.io
0.3.0-rc.10.3.0-rc.2
axum-core
crates.io
All versions0.2.8

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-770
    Allocation of Resources Without LimitsMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

Frequently Asked Questions

What is CVE-2022-3212?
axum-core has no default limit put on request bodies This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.5/10).
How do I check if my project is affected by CVE-2022-3212?
CVE-2022-3212 affects axum-core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2022-3212 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.5

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-m77f-652q-wwp4
RUSTSEC-2022-0055

Related CVEs

  • CVE-2026-93657
    HIGH

    hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures

  • CVE-2026-18140
    HIGH

    aws-smithy-json: Uncontrolled recursion in the aws-smithy-json unknown-key skip path allows unauthenticated remote denial of service in smithy-rs generated servers

More crates.io advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies