CVE-2022-3212
Axum Bytes Denial of Service (DoS)
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
INFO
Published Date :
Sept. 14, 2022, 4:15 p.m.
Last Modified :
Sept. 16, 2022, 7:22 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
3.9
Public PoC/Exploit Available at Github
CVE-2022-3212 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-3212.
| URL | Resource |
|---|---|
| https://research.jfrog.com/vulnerabilities/axum-core-dos/ | Exploit Third Party Advisory |
| https://rustsec.org/advisories/RUSTSEC-2022-0055.html | Exploit Issue Tracking Patch Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
This is a list of artifacts from the GitHub Advisory Database where the corresponding JSON files are missing CVE identifiers, despite the fact that these artifacts are listed in the NVD (National Vulnerability Database). I cross-referenced the data, retrieved the missing CVEs, and compiled everything into a list.
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-3212 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-3212 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Sep. 16, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://research.jfrog.com/vulnerabilities/axum-core-dos/ No Types Assigned https://research.jfrog.com/vulnerabilities/axum-core-dos/ Exploit, Third Party Advisory Changed Reference Type https://rustsec.org/advisories/RUSTSEC-2022-0055.html No Types Assigned https://rustsec.org/advisories/RUSTSEC-2022-0055.html Exploit, Issue Tracking, Patch, Third Party Advisory Added CWE NIST CWE-770 Added CPE Configuration OR *cpe:2.3:a:axum-core_project:axum-core:*:*:*:*:*:rust:*:* versions up to (excluding) 0.2.8 *cpe:2.3:a:axum-core_project:axum-core:0.3.0:rc1:*:*:*:rust:*:* -
CVE Modified by [email protected]
Sep. 14, 2022
Action Type Old Value New Value Changed 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 <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
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-3212 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-3212
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.08 }} 0.00%
score
0.31539
percentile