{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-16675 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16675 is a high-severity memory corruption vulnerability in n/a, published on 31 Oct 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-16675 and fix it if it is affected.\n\nWhat it is: CVE-2019-16675 is a high-severity memory corruption vulnerability in n/a, published on 31 Oct 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-16675 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-16675/ (Markdown: https://insights.sbomify.com/CVE-2019-16675/index.md)","id":"CVE-2019-16675","markdown":"https://insights.sbomify.com/CVE-2019-16675/index.md","name":"CVE-2019-16675","record":{"aliases":["GHSA-5f64-wpvq-45hw"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PLC programming software","requires_auth":"none","summary":"Attackers can achieve remote code execution by tricking users into opening manipulated project files 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":"config\\+","vendor":"phoenixcontact"},{"product":"pc_worx","vendor":"phoenixcontact"},{"product":"pc_worx_express","vendor":"phoenixcontact"}],"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-125","name":"Out-of-bounds Read"}],"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 Out-of-bounds Read and remote code execution. The attacker needs to get access to an original PC Worx or Config+ project to be able to manipulate data inside. After manipulation, the attacker needs to exchange the original files with the manipulated ones 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-16675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Improper Input Validation in simple_form","id":"CVE-2019-16676"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2019-16674"},"products":["n/a"],"published":"2019-10-31","related":[{"cvss_score":7.8,"headline":"Phoenix Contact: Automation Worx Software Suite affected by Remote Code Execution (RCE) vulnerability","id":"CVE-2021-33542","kev_date_added":null,"published":"2021-06-25"}],"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 achieve remote code execution by tricking users into opening manipulated project files in PHOENIX CONTACT PC Worx or Config+.","url":"https://insights.sbomify.com/CVE-2019-16675/"}