{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-12497 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12497 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12497 is a high-severity memory corruption vulnerability in Phoenix Contact Automation Worx, published on 1 Jul 2020. 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-2020-12497 and fix it if it is affected.\n\nWhat it is: CVE-2020-12497 is a high-severity memory corruption vulnerability in Phoenix Contact Automation Worx, published on 1 Jul 2020. 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-2020-12497 in the wild and no public exploit code.\n\nAffected product: Phoenix Contact Automation Worx. 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-2020-12497/ (Markdown: https://insights.sbomify.com/CVE-2020-12497/index.md)","id":"CVE-2020-12497","markdown":"https://insights.sbomify.com/CVE-2020-12497/index.md","name":"CVE-2020-12497","record":{"aliases":["GHSA-729h-mx93-mqwv"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","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 malicious PLCopen XML files in Phoenix Contact Automation Worx.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"pc_worx","vendor":"phoenixcontact"},{"product":"pc_worx_express","vendor":"phoenixcontact"}],"cvss":{"score":7.8,"severity":"high","source":"cna","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-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"PLCopen XML file parsing in Phoenix Contact PC Worx and PC Worx Express version 1.87 and earlier can lead to a stack-based overflow. Manipulated PC Worx projects could lead to a remote code execution due to insufficient input data validation.","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":"Phoenix Contact Automation Worx \u003c= 1.87: stack-based overflow","id":"CVE-2020-12497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Phoenix Contact Automation Worx \u003c= 1.87: out-of-bounds read remote code execution","id":"CVE-2020-12498"},"packages":[],"prev":{"headline":"Information disclosure in ORSG35 - Ecograph T Neutral/Private Label","id":"CVE-2020-12496"},"products":["Automation Worx","Automation Worx Express"],"published":"2020-07-01","related":[{"cvss_score":7.8,"headline":"Phoenix Contact: PC Worx/-Express prone to improper input validation vulnerability","id":"CVE-2021-34597","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":7.8,"headline":"Phoenix Contact Automation Worx \u003c= 1.87: out-of-bounds read remote code execution","id":"CVE-2020-12498","kev_date_added":null,"published":"2020-07-01"}],"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":["Phoenix Contact"]},"summary":"Attackers can achieve remote code execution by tricking users into opening malicious PLCopen XML files in Phoenix Contact Automation Worx.","url":"https://insights.sbomify.com/CVE-2020-12497/"}