{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17877 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17877 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17877 is a high-severity vulnerability in n/a, published on 23 Oct 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-17877 and fix it if it is affected.\n\nWhat it is: CVE-2018-17877 is a high-severity vulnerability in n/a, published on 23 Oct 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-17877 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-17877/ (Markdown: https://insights.sbomify.com/CVE-2018-17877/index.md)","id":"CVE-2018-17877","markdown":"https://insights.sbomify.com/CVE-2018-17877/index.md","name":"CVE-2018-17877","record":{"aliases":["GHSA-qp5m-38pc-fmj4"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum smart contract","requires_auth":"none","summary":"Attackers can predict random values in the Greedy 599 gambling contract to always win rewards, bypassing anti-contract checks.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"greedy_599","vendor":"greedy599"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"A lottery smart contract implementation for Greedy 599, an Ethereum gambling game, generates a random value that is predictable via an external contract call. The developer used the extcodesize() function to prevent a malicious contract from being called, but the attacker can bypass it by writing the core code in the constructor of their exploit code. Therefore, it allows attackers to always win and get rewards.","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-17877","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":"Memory corruption in n/a","id":"CVE-2018-17878"},"packages":[],"prev":{"headline":"Coaster CMS Stored Cross-site Scripting vulnerability","id":"CVE-2018-17876"},"products":["n/a"],"published":"2018-10-23","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":"Attackers can predict random values in the Greedy 599 gambling contract to always win rewards, bypassing anti-contract checks.","url":"https://insights.sbomify.com/CVE-2018-17877/"}