{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5172 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5172 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5172 is a high-severity command injection vulnerability in WAGO PFC200, published on 11 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-5172 and fix it if it is affected.\n\nWhat it is: CVE-2019-5172 is a high-severity command injection vulnerability in WAGO PFC200, published on 11 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-5172 in the wild and no public exploit code.\n\nAffected product: WAGO PFC200. 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-5172/ (Markdown: https://insights.sbomify.com/CVE-2019-5172/index.md)","id":"CVE-2019-5172","markdown":"https://insights.sbomify.com/CVE-2019-5172/index.md","name":"CVE-2019-5172","record":{"aliases":["GHSA-wxw5-4mj8-2m98"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WAGO PFC200 firmware","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary commands on WAGO PFC200 devices by sending a crafted packet to the iocheckd service.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"pfc200_firmware","vendor":"wago"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 Firmware version 03.02.02(14). An attacker can send a specially crafted packet to trigger the parsing of this cache file. At 0x1e840 the extracted ntp value from the xml file is used as an argument to /etc/config-tools/config_sntp time-server-%d=\u003ccontents of ntp node\u003e using sprintf(). This command is later executed via a call to system(). This is done in a loop and there is no limit to how many ntp entries will be parsed from the xml file.","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":"Command injection in WAGO PFC200","id":"CVE-2019-5172","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in WAGO PFC200","id":"CVE-2019-5173"},"packages":[],"prev":{"headline":"Command injection in WAGO PFC200","id":"CVE-2019-5171"},"products":["WAGO PFC200"],"published":"2020-03-11","related":[{"cvss_score":9.8,"headline":"Auth bypass in WAGO PFC200 Series","id":"CVE-2018-5459","kev_date_added":null,"published":"2018-02-13"},{"cvss_score":9.1,"headline":"Server-side request forgery in WAGO PFC200 Firmware","id":"CVE-2019-5160","kev_date_added":null,"published":"2020-03-10"},{"cvss_score":9.1,"headline":"Code injection in WAGO PFC200 Firmware","id":"CVE-2019-5161","kev_date_added":null,"published":"2020-03-10"},{"cvss_score":7.8,"headline":"Use after free in Wago","id":"CVE-2019-5184","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":7.8,"headline":"Command injection in WAGO PFC200","id":"CVE-2019-5169","kev_date_added":null,"published":"2020-03-11"},{"cvss_score":7.8,"headline":"Command injection in WAGO PFC200","id":"CVE-2019-5170","kev_date_added":null,"published":"2020-03-11"},{"cvss_score":7.8,"headline":"Command injection in WAGO PFC200","id":"CVE-2019-5171","kev_date_added":null,"published":"2020-03-11"}],"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":["Wago"]},"summary":"An attacker can execute arbitrary commands on WAGO PFC200 devices by sending a crafted packet to the iocheckd service.","url":"https://insights.sbomify.com/CVE-2019-5172/"}