{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39477 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39477 is a high-severity denial of service vulnerability in Inductive Automation Ignition, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-39477 and fix it if it is affected.\n\nWhat it is: CVE-2023-39477 is a high-severity denial of service vulnerability in Inductive Automation Ignition, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-39477 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-2023-39477/ (Markdown: https://insights.sbomify.com/CVE-2023-39477/index.md)","id":"CVE-2023-39477","markdown":"https://insights.sbomify.com/CVE-2023-39477/index.md","name":"CVE-2023-39477","record":{"aliases":["GHSA-g752-372v-qjj2"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial Automation Platform","requires_auth":"none","summary":"Remote attackers can cause denial of service in Inductive Automation Ignition by exhausting resources via OPC UA ConditionRefresh requests without authentication.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"ignition","vendor":"inductiveautomation"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Inductive Automation Ignition ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Inductive Automation Ignition. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of OPC UA ConditionRefresh requests. By sending a large number of requests, an attacker can consume all available resources on the server. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-20499.","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":"Inductive Automation Ignition ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability","id":"CVE-2023-39477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Softing Secure Integration Server Exposure of Resource to Wrong Sphere Remote Code Execution Vulnerability","id":"CVE-2023-39478"},"packages":[],"prev":{"headline":"Deserialization in Ignition","id":"CVE-2023-39476"},"products":["Ignition"],"published":"2024-05-03","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Inductive Automation"]},"summary":"Remote attackers can cause denial of service in Inductive Automation Ignition by exhausting resources via OPC UA ConditionRefresh requests without authentication.","url":"https://insights.sbomify.com/CVE-2023-39477/"}