{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35873 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35873 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35873 is a high-severity code injection vulnerability in Inductive Automation Ignition, published on 25 Jul 2022. 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-2022-35873 and fix it if it is affected.\n\nWhat it is: CVE-2022-35873 is a high-severity code injection vulnerability in Inductive Automation Ignition, published on 25 Jul 2022. 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-2022-35873 in the wild and no public exploit code.\n\nAffected product: Inductive Automation Ignition. 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-2022-35873/ (Markdown: https://insights.sbomify.com/CVE-2022-35873/index.md)","id":"CVE-2022-35873","markdown":"https://insights.sbomify.com/CVE-2022-35873/index.md","name":"CVE-2022-35873","record":{"aliases":["GHSA-6hm7-67pg-crfx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Industrial SCADA software","requires_auth":"none","summary":"Remote attackers can execute arbitrary Python scripts with SYSTEM privileges by tricking users into opening malicious ZIP files in Ignition.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"ignition","vendor":"inductiveautomation"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-356","name":"Missing User Interaction for Potentially Unsafe Action"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition 8.1.15 (b2022030114). User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of ZIP files. Crafted data in a ZIP file can cause the application to execute arbitrary Python scripts. The user interface fails to provide sufficient indication of the hazard. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-16949.","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 Ignition","id":"CVE-2022-35873","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in iota All-In-One Security Kit","id":"CVE-2022-35874"},"packages":[],"prev":{"headline":"Deserialization in Ignition","id":"CVE-2022-35872"},"products":["Ignition"],"published":"2022-07-25","related":[{"cvss_score":9.8,"headline":"Deserialization in Ignition","id":"CVE-2023-39475","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":9.8,"headline":"Deserialization in Ignition","id":"CVE-2023-39476","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-35890","kev_date_added":null,"published":"2022-07-15"},{"cvss_score":8.8,"headline":"Deserialization in Ignition","id":"CVE-2023-39473","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.8,"headline":"Inductive Automation Ignition ModuleInvoke Deserialization of Untrusted Data Remote Code Execution Vulnerability","id":"CVE-2023-50218","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.8,"headline":"Inductive Automation Ignition RunQuery Deserialization of Untrusted Data Remote Code Execution Vulnerability","id":"CVE-2023-50219","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.8,"headline":"Deserialization in Ignition","id":"CVE-2023-50221","kev_date_added":null,"published":"2024-05-03"}],"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-03","vendors":["Inductive Automation"]},"summary":"Remote attackers can execute arbitrary Python scripts with SYSTEM privileges by tricking users into opening malicious ZIP files in Ignition.","url":"https://insights.sbomify.com/CVE-2022-35873/"}