Skip to content

Duplicate of GHSA-m77f-652q-wwp4

High severity GitHub Reviewed Published Sep 15, 2022 to the GitHub Advisory Database • Updated Jan 28, 2023
Withdrawn This advisory was withdrawn on Sep 16, 2022

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

Duplicate advisory

This advisory is a duplicate of GHSA-m77f-652q-wwp4. This link is maintained to preserve external references.

Original 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

References

Published by the National Vulnerability Database Sep 14, 2022
Published to the GitHub Advisory Database Sep 15, 2022
Reviewed Sep 16, 2022
Withdrawn Sep 16, 2022
Last updated Jan 28, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-2gg5-7c4v-6xx2

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.