{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10610 is a high-severity memory corruption vulnerability in WECON Technology Co., Ltd LeviStudioU, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-10610 and fix it if it is affected.\n\nWhat it is: CVE-2018-10610 is a high-severity memory corruption vulnerability in WECON Technology Co., Ltd LeviStudioU, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-10610 in the wild and no public exploit code.\n\nAffected product: WECON Technology Co., Ltd LeviStudioU. 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-10610/ (Markdown: https://insights.sbomify.com/CVE-2018-10610/index.md)","id":"CVE-2018-10610","markdown":"https://insights.sbomify.com/CVE-2018-10610/index.md","name":"CVE-2018-10610","record":{"aliases":["GHSA-239j-vv78-jjcx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PLC programming software","requires_auth":"none","summary":"An out-of-bounds write in LeviStudioU allows attackers to execute arbitrary code via specially crafted project files.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"levistudiou","vendor":"we-con"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An out-of-bounds vulnerability in LeviStudioU, Versions 1.8.29 and 1.8.44 can be exploited when the application processes specially crafted project files.","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 LeviStudioU","id":"CVE-2018-10610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in MDS PulseNET and MDS PulseNET Enterprise","id":"CVE-2018-10611"},"packages":[],"prev":{"headline":"Cross-site scripting in TELEM-GW6/GWM","id":"CVE-2018-10609"},"products":["LeviStudioU"],"published":"2018-10-09","related":[{"cvss_score":8.8,"headline":"XML external entity in LeviStudioU","id":"CVE-2018-10614","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in LeviStudioU","id":"CVE-2018-10602","kev_date_added":null,"published":"2018-09-26"},{"cvss_score":8.8,"headline":"Memory corruption in LeviStudioU","id":"CVE-2018-10606","kev_date_added":null,"published":"2018-09-26"},{"cvss_score":7.8,"headline":"WECON LeviStudioU","id":"CVE-2021-23138","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":7.8,"headline":"WECON LeviStudioU","id":"CVE-2021-23157","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":7.8,"headline":"WECON LeviStudioU","id":"CVE-2021-43983","kev_date_added":null,"published":"2021-12-13"}],"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":["WECON Technology Co., Ltd"]},"summary":"An out-of-bounds write in LeviStudioU allows attackers to execute arbitrary code via specially crafted project files.","url":"https://insights.sbomify.com/CVE-2018-10610/"}