{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-54429 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54429 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54429 is a medium-severity vulnerability in polkadot-evm frontier, published on 28 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54429 and fix it if it is affected.\n\nWhat it is: CVE-2025-54429 is a medium-severity vulnerability in polkadot-evm frontier, published on 28 Jul 2025. 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-2025-54429 in the wild and no public exploit code.\n\nAffected product: polkadot-evm 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-2025-54429/ (Markdown: https://insights.sbomify.com/CVE-2025-54429/index.md)","id":"CVE-2025-54429","markdown":"https://insights.sbomify.com/CVE-2025-54429/index.md","name":"CVE-2025-54429","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Polkadot EVM compatibility layer","requires_auth":"none","summary":"Smart contracts can bypass access controls to call restricted precompiles due to incorrect address type identification in Polkadot Frontier.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"}],"description":"Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. There are various account address types in Frontier, e.g. precompiled contracts, smart contracts, and externally owned accounts. Some EVM mechanisms should be unreachable by certain types of accounts for safety. For precompiles to be callable by smart contracts they must be explicitly configured as CallableByContract. If this configuration is absent, then the precompile should be unreachable via smart contract accounts. In commits prior to 0822030, the underlying implementation of CallableByContract which returned the AddressType was incorrect. It considered the contract address running under CREATE or CREATE2 to be AddressType::EOA rather than correctly as AddressType::Contract. The issue only affects users who use custom precompile implementations that utilize AddressType::EOA and AddressType::Contract. It's not directly exploitable in any of the predefined precompiles in Frontier. This is fixed in version 0822030.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Polkadot Frontier's constructing smart contract can bypass precompile address bounding","id":"CVE-2025-54429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"dedupe is vulnerable to secret exfiltration via `issue_comment`","id":"CVE-2025-54430"},"packages":[],"prev":{"headline":"RevelaCode exposes Sensitive MongoDB Atlas URI in .env (potential credential leak)","id":"CVE-2025-54428"},"products":["frontier"],"published":"2025-07-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07-28","vendors":["polkadot-evm"]},"summary":"Smart contracts can bypass access controls to call restricted precompiles due to incorrect address type identification in Polkadot Frontier.","url":"https://insights.sbomify.com/CVE-2025-54429/"}