{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6090 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-6090 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-6090 is a high-severity code injection vulnerability in Wago, published on 11 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-6090 and fix it if it is affected.\n\nWhat it is: CVE-2020-6090 is a high-severity code injection vulnerability in Wago, published on 11 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-6090 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-2020-6090/ (Markdown: https://insights.sbomify.com/CVE-2020-6090/index.md)","id":"CVE-2020-6090","markdown":"https://insights.sbomify.com/CVE-2020-6090/index.md","name":"CVE-2020-6090","record":{"aliases":["GHSA-pjg3-ch5q-948j"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WAGO PFC 200 PLC","requires_auth":"high_privilege","summary":"An attacker with valid credentials can achieve remote code execution on WAGO PFC 200 controllers via crafted HTTP requests to the web management interface.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"pfc200_firmware","vendor":"wago"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"An exploitable code execution vulnerability exists in the Web-Based Management (WBM) functionality of WAGO PFC 200 03.03.10(15). A specially crafted series of HTTP requests can cause code execution resulting in remote code execution. An attacker can make an authenticated HTTP request to trigger this 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":"Code injection in Wago","id":"CVE-2020-6090","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Epson","id":"CVE-2020-6091"},"packages":[],"prev":{"headline":"Memory corruption in Leadtools","id":"CVE-2020-6089"},"products":["Wago"],"published":"2020-06-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":["n/a"]},"summary":"An attacker with valid credentials can achieve remote code execution on WAGO PFC 200 controllers via crafted HTTP requests to the web management interface.","url":"https://insights.sbomify.com/CVE-2020-6090/"}