{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11593 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11593 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11593 is a high-severity memory corruption vulnerability in n/a, published on 31 May 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-11593 and fix it if it is affected.\n\nWhat it is: CVE-2018-11593 is a high-severity memory corruption vulnerability in n/a, published on 31 May 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-11593 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-11593/ (Markdown: https://insights.sbomify.com/CVE-2018-11593/index.md)","id":"CVE-2018-11593","markdown":"https://insights.sbomify.com/CVE-2018-11593/index.md","name":"CVE-2018-11593","record":{"aliases":["GHSA-mhjc-hmmf-jc58"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Espruino JavaScript interpreter","requires_auth":"none","summary":"Attackers can cause application crashes and potential information disclosure via buffer overflow in syntax parsing using crafted input files.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"espruino","vendor":"espruino"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Espruino before 1.99 allows attackers to cause a denial of service (application crash) and potential Information Disclosure with a user crafted input file via a Buffer Overflow during syntax parsing because strncpy is misused in jslex.c.","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":"Memory corruption in n/a","id":"CVE-2018-11593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-11594"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-11592"},"products":["n/a"],"published":"2018-05-31","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-19693","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-22884","kev_date_added":null,"published":"2021-07-13"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-25044","kev_date_added":null,"published":"2022-03-05"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-25465","kev_date_added":null,"published":"2022-03-05"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-46324","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-46325","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2018-11595","kev_date_added":null,"published":"2018-05-31"}],"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":"Attackers can cause application crashes and potential information disclosure via buffer overflow in syntax parsing using crafted input files.","url":"https://insights.sbomify.com/CVE-2018-11593/"}