{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25837 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25837 is a high-severity vulnerability in n/a, published on 8 Feb 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-25837 and fix it if it is affected.\n\nWhat it is: CVE-2021-25837 is a high-severity vulnerability in n/a, published on 8 Feb 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-25837 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-25837/ (Markdown: https://insights.sbomify.com/CVE-2021-25837/index.md)","id":"CVE-2021-25837","markdown":"https://insights.sbomify.com/CVE-2021-25837/index.md","name":"CVE-2021-25837","record":{"aliases":[],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Cosmos Ethermint","requires_auth":"none","summary":"Attackers can exploit cache lifecycle inconsistencies in Ethermint to improperly reserve storage changes from failed transactions, enabling arbitrary token minting.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ethermint","vendor":"chainsafe"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Cosmos Network Ethermint \u003c= v0.4.0 is affected by cache lifecycle inconsistency in the EVM module. Due to the inconsistency between the Storage caching cycle and the Tx processing cycle, Storage changes caused by a failed transaction are improperly reserved in memory. Although the bad storage cache data will be discarded at EndBlock, it is still valid in the current block, which enables many possible attacks such as an \"arbitrary mint token\".","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-04-29","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-04-29T03:12:27Z","kind":"github_poc","ref":"https://github.com/iczc/Ethermint-CVE-2021-25837","stars":3,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"Business logic in n/a","id":"CVE-2021-25837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-25838"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2021-25836"},"products":["n/a"],"published":"2021-02-08","related":[{"cvss_score":7.5,"headline":"Authentication bypass by capture-replay in github.com/cosmos/ethermint","id":"CVE-2021-25834","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":7.5,"headline":"Authentication bypass by capture-replay in github.com/cosmos/ethermint","id":"CVE-2021-25835","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2021-25836","kev_date_added":null,"published":"2021-02-08"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can exploit cache lifecycle inconsistencies in Ethermint to improperly reserve storage changes from failed transactions, enabling arbitrary token minting.","url":"https://insights.sbomify.com/CVE-2021-25837/"}