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
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-6873 | <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 |
Github GHSA |
GHSA-m77f-652q-wwp4 | axum-core has no default limit put on request bodies |
References
History
Fri, 11 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Status: PUBLISHED
Assigner: JFROG
Published:
Updated: 2024-08-03T01:00:10.862Z
Reserved: 2022-09-14T00:00:00.000Z
Link: CVE-2022-3212
No data.
Status : Modified
Published: 2022-09-14T16:15:11.883
Modified: 2024-11-21T07:19:03.723
Link: CVE-2022-3212
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA