{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12870 is a high-severity memory corruption vulnerability in n/a, published on 24 Jun 2019. 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-2019-12870 and fix it if it is affected.\n\nWhat it is: CVE-2019-12870 is a high-severity memory corruption vulnerability in n/a, published on 24 Jun 2019. 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-2019-12870 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-2019-12870/ (Markdown: https://insights.sbomify.com/CVE-2019-12870/index.md)","id":"CVE-2019-12870","markdown":"https://insights.sbomify.com/CVE-2019-12870/index.md","name":"CVE-2019-12870","record":{"aliases":["GHSA-q6f5-9m85-j5v5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial PLC programming software","requires_auth":"none","summary":"Attackers can achieve remote code execution by tricking users into opening a manipulated project file in PHOENIX CONTACT PC Worx or Config+.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"automationworx_software_suite","vendor":"phoenixcontact"}],"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-824","name":"Access of Uninitialized Pointer"}],"description":"An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. A manipulated PC Worx or Config+ project file could lead to an Uninitialized Pointer and remote code execution. The attacker needs to get access to an original PC Worx or Config+ project file to be able to manipulate it. After manipulation, the attacker needs to exchange the original file with the manipulated one on the application programming workstation.","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-2019-12870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2019-12871"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-12869"},"products":["n/a"],"published":"2019-06-24","related":[{"cvss_score":9.8,"headline":"Missing authorization in AXC 1050","id":"CVE-2023-46141","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-12869","kev_date_added":null,"published":"2019-06-24"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2019-12871","kev_date_added":null,"published":"2019-06-24"},{"cvss_score":7.8,"headline":"Buffer Overflow in PHOENIX CONTACT Automationworx Software Suite","id":"CVE-2022-3461","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":7.8,"headline":"Out-of-bounds Read in PHOENIX CONTACT Automationworx Software Suite","id":"CVE-2022-3737","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":7.5,"headline":"Phoenix Contact: Classic line industrial controllers prone to inadequate integrity check of PLC","id":"CVE-2023-46143","kev_date_added":null,"published":"2023-12-14"}],"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-04","vendors":["n/a"]},"summary":"Attackers can achieve remote code execution by tricking users into opening a manipulated project file in PHOENIX CONTACT PC Worx or Config+.","url":"https://insights.sbomify.com/CVE-2019-12870/"}