{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18236 is a high-severity memory corruption vulnerability in WECON PLC Editor, published on 23 Dec 2019. 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-2019-18236 and fix it if it is affected.\n\nWhat it is: CVE-2019-18236 is a high-severity memory corruption vulnerability in WECON PLC Editor, published on 23 Dec 2019. 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-2019-18236 in the wild and no public exploit code.\n\nAffected product: WECON PLC Editor. 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-18236/ (Markdown: https://insights.sbomify.com/CVE-2019-18236/index.md)","id":"CVE-2019-18236","markdown":"https://insights.sbomify.com/CVE-2019-18236/index.md","name":"CVE-2019-18236","record":{"aliases":["GHSA-r2j3-2qwf-9h6r"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PLC programming software","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious project files in WECON PLC Editor.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"plc_editor","vendor":"we-con"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"Multiple buffer overflow vulnerabilities exist when the PLC Editor Version 1.3.5_20190129 processes project files. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.","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 WECON PLC Editor","id":"CVE-2019-18236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower","id":"CVE-2019-18238"},"packages":[],"prev":{"headline":"Auth bypass in Advantech Spectre RT ERT351 Versions 5.1.3 and prior","id":"CVE-2019-18235"},"products":["WECON PLC Editor"],"published":"2019-12-23","related":[{"cvss_score":8.8,"headline":"Memory corruption in WECON PLC Editor","id":"CVE-2020-25177","kev_date_added":null,"published":"2020-12-01"},{"cvss_score":8.8,"headline":"Memory corruption in WECON PLC Editor","id":"CVE-2020-25181","kev_date_added":null,"published":"2020-12-01"},{"cvss_score":7.8,"headline":"WECON PLC Editor","id":"CVE-2021-42705","kev_date_added":null,"published":"2021-11-22"},{"cvss_score":7.8,"headline":"WECON PLC Editor","id":"CVE-2021-42707","kev_date_added":null,"published":"2021-11-22"},{"cvss_score":6.3,"headline":"Code injection in PLC Editor","id":"CVE-2018-14792","kev_date_added":null,"published":"2018-09-19"}],"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":"Attackers can execute arbitrary code by tricking users into opening malicious project files in WECON PLC Editor.","url":"https://insights.sbomify.com/CVE-2019-18236/"}