{"answers":{"affected":"5 open source packages ship an affected version, including axum-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3212 in the wild and no public exploit code.","fix":"Upgrade axum-core to a fixed version for your release line: 0.2.8 or 0.3.0-rc.2.","what":"CVE-2022-3212 is a high-severity denial of service vulnerability in tokio-rs axum-core, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3212 and fix it if it is affected.\n\nWhat it is: CVE-2022-3212 is a high-severity denial of service vulnerability in tokio-rs axum-core, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-3212 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- axum-core (crates.io): affected all versions; fixed in 0.2.8\n- axum-core (crates.io): affected all versions; fixed in 0.2.8\n- axum-core (crates.io): affected from 0.0.0-0; fixed in 0.2.8, 0.3.0-rc.2\n- axum-core (crates.io): affected from 0.3.0-rc.1; fixed in 0.3.0-rc.2\n- axum-core (crates.io): affected from 0.3.0-rc.1; fixed in 0.3.0-rc.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-3212/ (Markdown: https://insights.sbomify.com/CVE-2022-3212/index.md)","id":"CVE-2022-3212","markdown":"https://insights.sbomify.com/CVE-2022-3212/index.md","name":"CVE-2022-3212","record":{"aliases":["GHSA-m77f-652q-wwp4","RUSTSEC-2022-0055"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust web framework","requires_auth":"none","summary":"Attackers can crash servers by sending excessively large request bodies due to missing default size limits in axum-core extractors.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"axum-core","vendor":"axum-core_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"\u003cbytes::Bytes as axum_core::extract::FromRequest\u003e::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","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"DoS in axum-core due to missing request size limit","id":"CVE-2022-3212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":5,"n_references":2,"next":{"headline":"Memory corruption in ImageMagick","id":"CVE-2022-3213"},"packages":[{"ecosystem":"crates.io","fixed":["0.2.8"],"introduced":["0"],"last_affected":[],"package":"axum-core","purl":null,"source":"GHSA-m77f-652q-wwp4"},{"ecosystem":"crates.io","fixed":["0.2.8"],"introduced":["0"],"last_affected":[],"package":"axum-core","purl":"pkg:cargo/axum-core","source":"GHSA-m77f-652q-wwp4"},{"ecosystem":"crates.io","fixed":["0.2.8","0.3.0-rc.2"],"introduced":["0.0.0-0","0.3.0-rc.1"],"last_affected":[],"package":"axum-core","purl":"pkg:cargo/axum-core","source":"RUSTSEC-2022-0055"},{"ecosystem":"crates.io","fixed":["0.3.0-rc.2"],"introduced":["0.3.0-rc.1"],"last_affected":[],"package":"axum-core","purl":null,"source":"GHSA-m77f-652q-wwp4"},{"ecosystem":"crates.io","fixed":["0.3.0-rc.2"],"introduced":["0.3.0-rc.1"],"last_affected":[],"package":"axum-core","purl":"pkg:cargo/axum-core","source":"GHSA-m77f-652q-wwp4"}],"prev":{"headline":"Cross-site Scripting (XSS) - Stored in pimcore/pimcore","id":"CVE-2022-3211"},"products":["axum-core"],"published":"2022-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["tokio-rs"]},"summary":"Attackers can crash servers by sending excessively large request bodies due to missing default size limits in axum-core extractors.","url":"https://insights.sbomify.com/CVE-2022-3212/"}