{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5184 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5184 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5184 is a high-severity use after free vulnerability in Wago, published on 23 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-5184 and fix it if it is affected.\n\nWhat it is: CVE-2019-5184 is a high-severity use after free vulnerability in Wago, published on 23 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-5184 in the wild and no public exploit code.\n\nAffected product: Wago. 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-5184/ (Markdown: https://insights.sbomify.com/CVE-2019-5184/index.md)","id":"CVE-2019-5184","markdown":"https://insights.sbomify.com/CVE-2019-5184/index.md","name":"CVE-2019-5184","record":{"aliases":["GHSA-rfcj-g83x-pvhm"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WAGO PFC 200","requires_auth":"low_privilege","summary":"A double free vulnerability in WAGO PFC 200 allows attackers to cause denial of service or execute code via crafted XML packets.","user_interaction":"not_required","vuln_class":"use_after_free"},"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-415","name":"Double Free"}],"description":"An exploitable double free vulnerability exists in the iocheckd service \"I/O-Check\" functionality of WAGO PFC 200. A specially crafted XML cache file written to a specific location on the device can cause a heap pointer to be freed twice, resulting in a denial of service and potentially code execution. An attacker can send a specially crafted packet to trigger the parsing of this cache 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":"Use after free in Wago","id":"CVE-2019-5184","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Wago","id":"CVE-2019-5185"},"packages":[],"prev":{"headline":"Memory corruption in AMD","id":"CVE-2019-5183"},"products":["Wago"],"published":"2020-03-23","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":"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":["n/a"]},"summary":"A double free vulnerability in WAGO PFC 200 allows attackers to cause denial of service or execute code via crafted XML packets.","url":"https://insights.sbomify.com/CVE-2019-5184/"}