{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5159 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5159 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5159 is a high-severity path traversal vulnerability in WAGO e!COCKPIT, published on 10 Mar 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-2019-5159 and fix it if it is affected.\n\nWhat it is: CVE-2019-5159 is a high-severity path traversal vulnerability in WAGO e!COCKPIT, published on 10 Mar 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-2019-5159 in the wild and no public exploit code.\n\nAffected product: WAGO e!COCKPIT. 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-5159/ (Markdown: https://insights.sbomify.com/CVE-2019-5159/index.md)","id":"CVE-2019-5159","markdown":"https://insights.sbomify.com/CVE-2019-5159/index.md","name":"CVE-2019-5159","record":{"aliases":["GHSA-f5w9-64vw-8wmq"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WAGO e!COCKPIT","requires_auth":"none","summary":"Attackers can achieve code execution on WAGO controllers by tricking users into installing a malicious firmware update file containing arbitrary file writes.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"e\\!cockpit","vendor":"wago"}],"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-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"An exploitable improper input validation vulnerability exists in the firmware update functionality of WAGO e!COCKPIT automation software v1.6.0.7. A specially crafted firmware update file can allow an attacker to write arbitrary files to arbitrary locations on WAGO controllers as a part of executing a firmware update, potentially resulting in code execution. An attacker can create a malicious firmware update package file using any zip utility. The user must initiate a firmware update through e!COCKPIT and choose the malicious wup file using the file browser to trigger the vulnerability.","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":"Path traversal in WAGO e!COCKPIT","id":"CVE-2019-5159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in WAGO PFC200 Firmware","id":"CVE-2019-5160"},"packages":[],"prev":{"headline":"Security feature bypass in WAGO e!COCKPIT","id":"CVE-2019-5158"},"products":["WAGO e!COCKPIT"],"published":"2020-03-10","related":[{"cvss_score":7.8,"headline":"Security feature bypass in WAGO e!COCKPIT","id":"CVE-2019-5158","kev_date_added":null,"published":"2020-03-10"},{"cvss_score":7.5,"headline":"Information disclosure in WAGO e!Cockpit","id":"CVE-2019-5107","kev_date_added":null,"published":"2020-03-10"},{"cvss_score":5.5,"headline":"Hardcoded credentials in WAGO e!Cockpit","id":"CVE-2019-5106","kev_date_added":null,"published":"2020-03-10"}],"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":"Attackers can achieve code execution on WAGO controllers by tricking users into installing a malicious firmware update file containing arbitrary file writes.","url":"https://insights.sbomify.com/CVE-2019-5159/"}