{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14085 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14085 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14085 is a high-severity vulnerability in n/a, published on 16 Jul 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-14085 and fix it if it is affected.\n\nWhat it is: CVE-2018-14085 is a high-severity vulnerability in n/a, published on 16 Jul 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-14085 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-14085/ (Markdown: https://insights.sbomify.com/CVE-2018-14085/index.md)","id":"CVE-2018-14085","markdown":"https://insights.sbomify.com/CVE-2018-14085/index.md","name":"CVE-2018-14085","record":{"aliases":["GHSA-h6pf-g657-4j3g"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum smart contract","requires_auth":"none","summary":"An attacker can manipulate the sweeper list in the UserWallet smart contract by adding a malicious contract, altering internal state variables.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"userwallet","vendor":"userwallet_project"}],"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"}],"description":"An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function sweep(address _token, uint _amount) returns (bool) { start = 0x123456789; return true;} }. Then, when one calls the function sweep() in the UserWallet contract, it will change the sweeperList to 0X123456789.","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-14085","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":"Integer overflow in n/a","id":"CVE-2018-14086"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2018-14084"},"products":["n/a"],"published":"2018-07-16","related":[],"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-09-16","vendors":["n/a"]},"summary":"An attacker can manipulate the sweeper list in the UserWallet smart contract by adding a malicious contract, altering internal state variables.","url":"https://insights.sbomify.com/CVE-2018-14085/"}