{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-13710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-13710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-13710 is a high-severity vulnerability in n/a, published on 9 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-13710 and fix it if it is affected.\n\nWhat it is: CVE-2018-13710 is a high-severity vulnerability in n/a, published on 9 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-13710 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-13710/ (Markdown: https://insights.sbomify.com/CVE-2018-13710/index.md)","id":"CVE-2018-13710","markdown":"https://insights.sbomify.com/CVE-2018-13710/index.md","name":"CVE-2018-13710","record":{"aliases":["GHSA-2wfv-2pmr-5vfx"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum smart contract","requires_auth":"none","summary":"An integer overflow in the Mjolnir token contract allows the owner to arbitrarily set any user's balance, compromising token integrity.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mjolnir","vendor":"mjolnir_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-190","name":"Integer Overflow or Wraparound"}],"description":"The mintToken function of a smart contract implementation for Mjolnir, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.","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":"Integer overflow in n/a","id":"CVE-2018-13710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2018-13711"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2018-13709"},"products":["n/a"],"published":"2018-07-09","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":"An integer overflow in the Mjolnir token contract allows the owner to arbitrarily set any user's balance, compromising token integrity.","url":"https://insights.sbomify.com/CVE-2018-13710/"}