{"containers": {"cna": {"affected": [{"product": "axum-core", "vendor": "tokio-rs", "versions": [{"status": "affected", "version": "0.3.0-rc.1"}, {"lessThan": "0.2.8", "status": "affected", "version": "unspecified", "versionType": "custom"}]}], "descriptions": [{"lang": "en", "value": "<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"}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-770", "description": "CWE-770 Allocation of Resources Without Limits or Throttling", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"dateUpdated": "2022-09-14T16:05:09", "orgId": "48a46f29-ae42-4e1d-90dd-c1676c1e5e6d", "shortName": "JFROG"}, "references": [{"tags": ["x_refsource_MISC"], "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"}, {"tags": ["x_refsource_MISC"], "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}], "title": "DoS in axum-core due to missing request size limit", "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "security@jfrog.com", "ID": "CVE-2022-3212", "STATE": "PUBLIC", "TITLE": "DoS in axum-core due to missing request size limit"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "axum-core", "version": {"version_data": [{"platform": "", "version_affected": "<", "version_name": "", "version_value": "0.2.8"}, {"platform": "", "version_affected": "=", "version_name": "", "version_value": "0.3.0-rc.1"}]}}]}, "vendor_name": "tokio-rs"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "<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"}]}, "impact": {"cvss": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "CWE-770 Allocation of Resources Without Limits or Throttling"}]}]}, "references": {"reference_data": [{"name": "https://research.jfrog.com/vulnerabilities/axum-core-dos/", "refsource": "MISC", "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"}, {"name": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html", "refsource": "MISC", "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}]}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-03T01:00:10.862Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}]}]}, "cveMetadata": {"assignerOrgId": "48a46f29-ae42-4e1d-90dd-c1676c1e5e6d", "assignerShortName": "JFROG", "cveId": "CVE-2022-3212", "datePublished": "2022-09-14T16:05:09", "dateReserved": "2022-09-14T00:00:00", "dateUpdated": "2024-08-03T01:00:10.862Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:axum-core_project:axum-core:*:*:*:*:*:rust:*:*", "matchCriteriaId": "3C75C001-9583-4589-B223-CFC88D83DC6F", "versionEndExcluding": "0.2.8", "vulnerable": true}, {"criteria": "cpe:2.3:a:axum-core_project:axum-core:0.3.0:rc1:*:*:*:rust:*:*", "matchCriteriaId": "BAA28945-A516-4F1E-99FF-470141986E69", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "descriptions": [{"lang": "en", "value": "<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"}, {"lang": "es", "value": "(bytes::Bytes como axum_core::extract::FromRequest)::from_request no establec\u00eda, por defecto, un l\u00edmite para el tama\u00f1o del cuerpo de la petici\u00f3n. Esto significaba que si un compa\u00f1ero malicioso enviaba un cuerpo muy grande (o infinito) su servidor podr\u00eda quedarse sin memoria y colapsar. Esto tambi\u00e9n se aplica a estos extractores que usan Bytes::from_request internamente: axum::extract::Form axum::extract::Json String"}], "id": "CVE-2022-3212", "lastModified": "2024-11-21T07:19:03.723", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "reefs@jfrog.com", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2022-09-14T16:15:11.883", "references": [{"source": "reefs@jfrog.com", "tags": ["Exploit", "Third Party Advisory"], "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"}, {"source": "reefs@jfrog.com", "tags": ["Exploit", "Issue Tracking", "Patch", "Third Party Advisory"], "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Third Party Advisory"], "url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Issue Tracking", "Patch", "Third Party Advisory"], "url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"}], "sourceIdentifier": "reefs@jfrog.com", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-770"}], "source": "reefs@jfrog.com", "type": "Secondary"}, {"description": [{"lang": "en", "value": "CWE-770"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{}