Files
vuln-osv/data/crates.io/RUSTSEC-2022-0055.json
T

1 line
1.7 KiB
JSON

{"schema_version":"1.7.3","id":"RUSTSEC-2022-0055","published":"2022-08-31T12:00:00Z","modified":"2023-11-08T04:09:34.414125Z","aliases":["CVE-2022-3212","GHSA-m77f-652q-wwp4"],"summary":"No default limit put on request bodies","details":"`<bytes::Bytes as axum_core::extract::FromRequest>::from_request` would not, by\ndefault, set a limit for the size of the request body. That meant if a malicious\npeer would send a very large (or infinite) body your server might run out of\nmemory and crash.\n\nThis also applies to these extractors which used `Bytes::from_request`\ninternally:\n- `axum::extract::Form`\n- `axum::extract::Json`\n- `String`\n\nThe fix is also in `axum-core` `0.3.0.rc.2` but `0.3.0.rc.1` _is_ vulnerable.\n\nBecause `axum` depends on `axum-core` it is vulnerable as well. The vulnerable\nversions of `axum` are `<= 0.5.15` and `0.6.0.rc.1`. `axum` `>= 0.5.16` and\n`>= 0.6.0.rc.2` does have the fix and are not vulnerable.\n\nThe patched versions will set a 2 MB limit by default.","affected":[{"package":{"name":"axum-core","ecosystem":"crates.io","purl":"pkg:cargo/axum-core"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.2.8"},{"introduced":"0.3.0-rc.1"},{"fixed":"0.3.0-rc.2"}]}],"ecosystem_specific":{"affected_functions":null,"affects":{"arch":[],"functions":[],"os":[]}},"database_specific":{"categories":["denial-of-service"],"cvss":null,"informational":null,"source":"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2022-0055.json"}}],"references":[{"type":"PACKAGE","url":"https://crates.io/crates/axum-core"},{"type":"ADVISORY","url":"https://rustsec.org/advisories/RUSTSEC-2022-0055.html"},{"type":"WEB","url":"https://github.com/tokio-rs/axum/pull/1346"}],"database_specific":{"license":"CC0-1.0"}}