Skip to content

axum-core has no default limit put on request bodies

High severity GitHub Reviewed Published Sep 15, 2022 to the GitHub Advisory Database • Updated Jan 12, 2023

Package

cargo axum-core (Rust)

Affected versions

< 0.2.8
= 0.3.0-rc.1

Patched versions

0.2.8
0.3.0-rc.2

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

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.

References

Published to the GitHub Advisory Database Sep 15, 2022
Reviewed Sep 15, 2022
Last updated Jan 12, 2023

Severity

High
7.5
/ 10

CVSS base metrics

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

Weaknesses

CVE ID

CVE-2022-3212

GHSA ID

GHSA-m77f-652q-wwp4

Source code

Checking history
See something to contribute? Suggest improvements for this vulnerability.