{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12025 is a high-severity vulnerability in n/a, published on 11 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12025 and fix it if it is affected.\n\nWhat it is: CVE-2018-12025 is a high-severity vulnerability in n/a, published on 11 Jun 2018. 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-2018-12025 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-2018-12025/ (Markdown: https://insights.sbomify.com/CVE-2018-12025/index.md)","id":"CVE-2018-12025","markdown":"https://insights.sbomify.com/CVE-2018-12025/index.md","name":"CVE-2018-12025","record":{"aliases":["GHSA-36w2-wp3m-gg7j"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum smart contract","requires_auth":"none","summary":"Attackers can steal FuturXE tokens from any account due to a flawed allowance check in the transferFrom function.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"futurxe","vendor":"futurxe"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"The transferFrom function of a smart contract implementation for FuturXE (FXE), an Ethereum ERC20 token, allows attackers to accomplish an unauthorized transfer of digital assets because of a logic error. The developer messed up with the boolean judgment - if the input value is smaller than or equal to allowed value, the transfer session would stop execution by returning false. This makes no sense, because the transferFrom() function should require the transferring value to not exceed the allowed value in the first place. Suppose this function asks for the allowed value to be smaller than the input. Then, the attacker could easily ignore the allowance: after this condition, the `allowed[from][msg.sender] -= value;` would cause an underflow because the allowed part is smaller than the value. The attacker could transfer any amount of FuturXe tokens of any accounts to an appointed account (the `_to` address) because the allowed value is initialized to 0, and the attacker could bypass this restriction even without the victim's private key.","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":"Business logic in n/a","id":"CVE-2018-12025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Phusion Passenger SpawningKit Contains Arbitrary Read/Write Vulnerability","id":"CVE-2018-12026"},"packages":[],"prev":{"headline":"Deserialization of Untrusted Data","id":"CVE-2018-12023"},"products":["n/a"],"published":"2018-06-11","related":[{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2018-13718","kev_date_added":null,"published":"2018-07-09"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can steal FuturXE tokens from any account due to a flawed allowance check in the transferFrom function.","url":"https://insights.sbomify.com/CVE-2018-12025/"}