CVE-2021-41138

{"id": "CVE-2021-41138", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2021-10-13T16:15:07.847", "references": [{"url": "https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/paritytech/frontier/pull/497", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/paritytech/frontier/security/advisories/GHSA-vj62-g63v-f8mf", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/paritytech/frontier/pull/497", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/paritytech/frontier/security/advisories/GHSA-vj62-g63v-f8mf", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-20"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "Frontier is Substrate's Ethereum compatibility layer. In the newly introduced signed Frontier-specific extrinsic for `pallet-ethereum`, a large part of transaction validation logic was only called in transaction pool validation, but not in block execution. Malicious validators can take advantage of this to put invalid transactions into a block. The attack is limited in that the signature is always validated, and the majority of the validation is done again in the subsequent `pallet-evm` execution logic. However, do note that a chain ID replay attack was possible. In addition, spamming attacks are of main concerns, while they are limited by Substrate block size limits and other factors. The issue is patched in commit `146bb48849e5393004be5c88beefe76fdf009aba`."}, {"lang": "es", "value": "Frontier es la capa de compatibilidad con Ethereum de Substrate. En la reci\u00e9n introducida extr\u00ednseca espec\u00edfica de Frontier para \"pallet-ethereum\", una gran parte de la l\u00f3gica de comprobaci\u00f3n de transacciones s\u00f3lo se llamaba en la comprobaci\u00f3n del conjunto de transacciones, pero no en la ejecuci\u00f3n del bloque. Los comprobadores maliciosos pueden aprovechar esto para poner transacciones no v\u00e1lidas en un bloque. El ataque est\u00e1 limitado en el sentido de que la firma siempre es validada, y la mayor parte de la comprobaci\u00f3n es realizada de nuevo en la l\u00f3gica de ejecuci\u00f3n posterior de \"pallet-evm\". Sin embargo, es debido tener en cuenta que es posible un ataque de repetici\u00f3n de ID de cadena. Adem\u00e1s, los ataques de spam son de las principales preocupaciones, mientras que est\u00e1n limitados por los l\u00edmites de tama\u00f1o de bloque del sustrato y otros factores. El problema est\u00e1 parcheado en el commit \"146bb48849e5393004be5c88beefe76fdf009aba\""}], "lastModified": "2024-11-21T06:25:34.130", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:parity:frontier:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "DFC2C906-5789-4816-87DF-5EB4B6760564", "versionEndExcluding": "2021-10-13", "versionStartIncluding": "2021-09-30"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}