{"answers":{"affected":"2 open source packages ship an affected version, including fc-rpc. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36008 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36008 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36008 is a high-severity vulnerability in paritytech frontier, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36008 and fix it if it is affected.\n\nWhat it is: CVE-2022-36008 is a high-severity vulnerability in paritytech frontier, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36008 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fc-rpc (crates.io): affected all versions up to 1.0.0; no fix listed\n- fc-rpc (crates.io): affected all versions up to 1.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-2022-36008/ (Markdown: https://insights.sbomify.com/CVE-2022-36008/index.md)","id":"CVE-2022-36008","markdown":"https://insights.sbomify.com/CVE-2022-36008/index.md","name":"CVE-2022-36008","record":{"aliases":["GHSA-mjvm-mhgc-q4gp"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Substrate Ethereum compatibility layer","requires_auth":"low_privilege","summary":"An integer overflow in Frontier's RPC result parsing causes a panic in debug builds, leading to denial of service for bridge nodes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"frontier","vendor":"parity"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Frontier is Substrate's Ethereum compatibility layer. A security issue was discovered affecting parsing of the RPC result of the exit reason in case of EVM reversion. In release build, this would cause the exit reason being incorrectly parsed and returned by RPC. In debug build, this would cause an overflow panic. No action is needed unless you have a bridge node that needs to distinguish different reversion exit reasons and you used RPC for this. There are currently no known workarounds.","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":"Message length overflow in frontier","id":"CVE-2022-36008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":2,"n_references":3,"next":{"headline":"Incorrect parsing of access level in gomatrixserverlib and dendrite","id":"CVE-2022-36009"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"fc-rpc","purl":null,"source":"GHSA-mjvm-mhgc-q4gp"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"fc-rpc","purl":"pkg:cargo/fc-rpc","source":"GHSA-mjvm-mhgc-q4gp"}],"prev":{"headline":"Partial Path Traversal in com.github.jlangch:venice","id":"CVE-2022-36007"},"products":["frontier"],"published":"2022-08-19","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":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"},{"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":"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["paritytech"]},"summary":"An integer overflow in Frontier's RPC result parsing causes a panic in debug builds, leading to denial of service for bridge nodes.","url":"https://insights.sbomify.com/CVE-2022-36008/"}