{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18425 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18425 and fix it if it is affected.\n\nWhat it is: CVE-2018-18425 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-18425 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-18425/ (Markdown: https://insights.sbomify.com/CVE-2018-18425/index.md)","id":"CVE-2018-18425","markdown":"https://insights.sbomify.com/CVE-2018-18425/index.md","name":"CVE-2018-18425","record":{"aliases":["GHSA-7qvr-f99m-rpch"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum smart contract","requires_auth":"low_privilege","summary":"Contract owner can issue arbitrary tokens by bypassing supply caps, devaluing the asset for all holders.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"primeo","vendor":"primeo_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"The doAirdrop function of a smart contract implementation for Primeo (PEO), an Ethereum token, does not check the numerical relationship between the amount of the air drop and the token's total supply, which lets the owner of the contract issue an arbitrary amount of currency. (Increasing the total supply by using 'doAirdrop' ignores the hard cap written in the contract and devalues the token.)","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-18425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2018-18426"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-18422"},"products":["n/a"],"published":"2019-06-19","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-08-05","vendors":["n/a"]},"summary":"Contract owner can issue arbitrary tokens by bypassing supply caps, devaluing the asset for all holders.","url":"https://insights.sbomify.com/CVE-2018-18425/"}