Ecosyste.ms: Advisories

Security Advisories: GSA_kwCzR0hTQS1tNzdmLTY1MnEtd3dwNM4AAuzu

axum-core has no default limit put on request bodies

<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.

Permalink: https://github.com/advisories/GHSA-m77f-652q-wwp4
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS1tNzdmLTY1MnEtd3dwNM4AAuzu
Source: GitHub Advisory Database
Origin: Unspecified
Severity: High
Classification: General
Published: about 2 years ago
Updated: almost 2 years ago

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

Identifiers: GHSA-m77f-652q-wwp4, CVE-2022-3212
References:

• https://github.com/tokio-rs/axum/pull/1346
• https://rustsec.org/advisories/RUSTSEC-2022-0055.html
• https://nvd.nist.gov/vuln/detail/CVE-2022-3212
• https://github.com/advisories/GHSA-m77f-652q-wwp4

Repository: https://github.com/tokio-rs/axum
Blast Radius: 27.4

Affected Packages