{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15079 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15079 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15079 is a high-severity vulnerability in n/a, published on 30 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15079 and fix it if it is affected.\n\nWhat it is: CVE-2019-15079 is a high-severity vulnerability in n/a, published on 30 Dec 2020. 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-2019-15079 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-2019-15079/ (Markdown: https://insights.sbomify.com/CVE-2019-15079/index.md)","id":"CVE-2019-15079","markdown":"https://insights.sbomify.com/CVE-2019-15079/index.md","name":"CVE-2019-15079","record":{"aliases":["GHSA-99wx-928f-hqw6"],"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":"A typo in the smart contract constructor allows attackers to acquire EAI tokens for free, impacting token holders and the token economy.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"eai","vendor":"eai_project"}],"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":"A typo exists in the constructor of a smart contract implementation for EAI through 2019-06-05, an Ethereum token. This vulnerability could be used by an attacker to acquire EAI tokens for free.","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-2019-15079","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2019-15080"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2019-15078"},"products":["n/a"],"published":"2020-12-30","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A typo in the smart contract constructor allows attackers to acquire EAI tokens for free, impacting token holders and the token economy.","url":"https://insights.sbomify.com/CVE-2019-15079/"}