{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18749 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18749 is a medium-severity vulnerability in n/a, published on 28 Oct 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-18749 and fix it if it is affected.\n\nWhat it is: CVE-2018-18749 is a medium-severity vulnerability in n/a, published on 28 Oct 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-18749 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-18749/ (Markdown: https://insights.sbomify.com/CVE-2018-18749/index.md)","id":"CVE-2018-18749","markdown":"https://insights.sbomify.com/CVE-2018-18749/index.md","name":"CVE-2018-18749","record":{"aliases":["GHSA-7cwm-5vpw-qj96"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"data-tools library","requires_auth":"none","summary":"An integer overflow in the write_wchars function of the data-tools library can lead to memory corruption or crashes.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"data_tools","vendor":"data_tools_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"data-tools through 2017-07-26 has an Integer Overflow leading to an incorrect end value for the write_wchars function.","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-18749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in n/a","id":"CVE-2018-18751"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-18748"},"products":["n/a"],"published":"2018-10-28","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 integer overflow in the write_wchars function of the data-tools library can lead to memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2018-18749/"}