{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2277 is a high-severity denial of service vulnerability in Hitachi Energy MicroSCADA X SYS600, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2277 and fix it if it is affected.\n\nWhat it is: CVE-2022-2277 is a high-severity denial of service vulnerability in Hitachi Energy MicroSCADA X SYS600, published on 14 Sep 2022. 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-2022-2277 in the wild and no public exploit code.\n\nAffected product: Hitachi Energy MicroSCADA X SYS600. 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-2277/ (Markdown: https://insights.sbomify.com/CVE-2022-2277/index.md)","id":"CVE-2022-2277","markdown":"https://insights.sbomify.com/CVE-2022-2277/index.md","name":"CVE-2022-2277","record":{"aliases":["GHSA-m8wx-w8wv-8q47"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"SCADA system","requires_auth":"none","summary":"Attackers can cause denial of service in Hitachi MicroSCADA X SYS600 by sending ICCP data with future timestamps, requiring ICCP to be enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Hitachi Energy","cpe":[{"product":"microscada_x_sys600","vendor":"hitachienergy"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"Improper Input Validation vulnerability exists in the Hitachi Energy MicroSCADA X SYS600's ICCP stack during the ICCP communication establishment causes a denial-of-service when ICCP of SYS600 is request to forward any data item updates with timestamps too distant in the future to any remote ICCP system. By default, ICCP is not configured and not enabled. This issue affects: Hitachi Energy MicroSCADA X SYS600 version 10.2 to version 10.3.1. cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3.1:*:*:*:*:*:*:*","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":"Denial of service in MicroSCADA X SYS600","id":"CVE-2022-2277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Featured Image from URL \u003c 4.0.1 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-2278"},"packages":[],"prev":{"headline":"WP Edit Menu \u003c 1.5.0 - Unauthenticated Arbitrary Post Deletion","id":"CVE-2022-2276"},"products":["MicroSCADA X SYS600"],"published":"2022-09-14","related":[{"cvss_score":8.5,"headline":"Missing authorization in MicroSCADA SYS600","id":"CVE-2026-9853","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Privilege escalation in MicroSCADA SYS600","id":"CVE-2026-9854","kev_date_added":null,"published":"2026-09-03"},{"cvss_score":8.5,"headline":"Information disclosure in MicroSCADA X SYS600","id":"CVE-2025-39204","kev_date_added":null,"published":"2025-06-24"},{"cvss_score":8.5,"headline":"Missing authorization in MicroSCADA X SYS600","id":"CVE-2022-29490","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":8.3,"headline":"Missing authorization in MicroSCADA X SYS600","id":"CVE-2025-39202","kev_date_added":null,"published":"2025-06-24"},{"cvss_score":8.3,"headline":"Missing authorization in MicroSCADA SYS600","id":"CVE-2024-7940","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":8.2,"headline":"Auth bypass in MicroSCADA SYS600","id":"CVE-2024-3982","kev_date_added":null,"published":"2024-08-27"}],"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":"2025-06-04","vendors":["Hitachi Energy"]},"summary":"Attackers can cause denial of service in Hitachi MicroSCADA X SYS600 by sending ICCP data with future timestamps, requiring ICCP to be enabled.","url":"https://insights.sbomify.com/CVE-2022-2277/"}