{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31111 is a medium-severity vulnerability in paritytech frontier, published on 6 Jul 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-31111 and fix it if it is affected.\n\nWhat it is: CVE-2022-31111 is a medium-severity vulnerability in paritytech frontier, published on 6 Jul 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-31111 in the wild and no public exploit code.\n\nAffected product: paritytech frontier. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-31111/ (Markdown: https://insights.sbomify.com/CVE-2022-31111/index.md)","id":"CVE-2022-31111","markdown":"https://insights.sbomify.com/CVE-2022-31111/index.md","name":"CVE-2022-31111","record":{"aliases":["GHSA-hc8w-mx86-9fcj"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Substrate Ethereum compatibility layer","requires_auth":"none","summary":"Incorrect truncation in Frontier causes discrepancies between displayed and actual transferred values, requiring an upgrade to fix.","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-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Frontier is Substrate's Ethereum compatibility layer. In affected versions the truncation done when converting between EVM balance type and Substrate balance type was incorrectly implemented. This leads to possible discrepancy between appeared EVM transfer value and actual Substrate value transferred. It is recommended that an emergency upgrade to be planned and EVM execution temporarily paused in the mean time. The issue is patched in Frontier master branch commit fed5e0a9577c10bea021721e8c2c5c378e16bf66 and polkadot-v0.9.22 branch commit e3e427fa2e5d1200a784679f8015d4774cedc934. This vulnerability affects only EVM internal states, but not Substrate balance states or node. You can temporarily pause EVM execution (by setting up a Substrate `CallFilter` that disables `pallet-evm` and `pallet-ethereum` calls before the patch can be applied.","ecosystems":[],"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":"Discrepency in transfer value and actual value due to incorrect truncation in Frontier","id":"CVE-2022-31111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Protected fields exposed via LiveQuery in parse-server","id":"CVE-2022-31112"},"packages":[],"prev":{"headline":"Denial of Service (DoS) vulnerability in RSSHub","id":"CVE-2022-31110"},"products":["frontier"],"published":"2022-07-06","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":"Validity check for signed Frontier-specific extrinsic not called in block execution","id":"CVE-2021-41138","kev_date_added":null,"published":"2021-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["paritytech"]},"summary":"Incorrect truncation in Frontier causes discrepancies between displayed and actual transferred values, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2022-31111/"}