{"answers":{"affected":"2 open source packages ship an affected version, including pallet-ethereum. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41138 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41138 is a medium-severity vulnerability in paritytech frontier, published on 13 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41138 and fix it if it is affected.\n\nWhat it is: CVE-2021-41138 is a medium-severity vulnerability in paritytech frontier, published on 13 Oct 2021. 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-2021-41138 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pallet-ethereum (crates.io): affected all versions up to 3.0.0; no fix listed\n- pallet-ethereum (crates.io): affected all versions up to 3.0.0; no fix listed\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-2021-41138/ (Markdown: https://insights.sbomify.com/CVE-2021-41138/index.md)","id":"CVE-2021-41138","markdown":"https://insights.sbomify.com/CVE-2021-41138/index.md","name":"CVE-2021-41138","record":{"aliases":["GHSA-vj62-g63v-f8mf"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Substrate Ethereum compatibility","requires_auth":"none","summary":"Malicious validators can insert invalid transactions into blocks due to missing validation during execution, enabling chain ID replay attacks and spam.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"frontier","vendor":"parity"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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`.","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":false,"headline":"Validity check for signed Frontier-specific extrinsic not called in block execution","id":"CVE-2021-41138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Reflected XSS vulnerability in time.php","id":"CVE-2021-41139"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["3.0.0"],"package":"pallet-ethereum","purl":null,"source":"GHSA-vj62-g63v-f8mf"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["3.0.0"],"package":"pallet-ethereum","purl":"pkg:cargo/pallet-ethereum","source":"GHSA-vj62-g63v-f8mf"}],"prev":{"headline":"Bypassing policy restrictions on regular users","id":"CVE-2021-41137"},"products":["frontier"],"published":"2021-10-13","related":[{"cvss_score":7.5,"headline":"Frontier opcode SUICIDE touches too many storage values on large contracts","id":"CVE-2023-45130","kev_date_added":null,"published":"2023-10-13"},{"cvss_score":7.5,"headline":"Frontier's modexp precompile is slow for even modulus","id":"CVE-2023-28431","kev_date_added":null,"published":"2023-03-22"},{"cvss_score":7.1,"headline":"Message length overflow in frontier","id":"CVE-2022-36008","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":6.5,"headline":"Integer underflow in Frontier","id":"CVE-2022-21685","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":5.3,"headline":"Incorrect Calculation in Frontier leads to inflated Ethereum chain gas prices","id":"CVE-2022-39242","kev_date_added":null,"published":"2022-09-24"},{"cvss_score":5.3,"headline":"Discrepency in transfer value and actual value due to incorrect truncation in Frontier","id":"CVE-2022-31111","kev_date_added":null,"published":"2022-07-06"}],"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":"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-04","vendors":["paritytech"]},"summary":"Malicious validators can insert invalid transactions into blocks due to missing validation during execution, enabling chain ID replay attacks and spam.","url":"https://insights.sbomify.com/CVE-2021-41138/"}