{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1667 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1667 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1667 is a high-severity missing authorization vulnerability in Secheron SEPCOS Control and Protection Relay firmware package, published on 24 Jun 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-1667 and fix it if it is affected.\n\nWhat it is: CVE-2022-1667 is a high-severity missing authorization vulnerability in Secheron SEPCOS Control and Protection Relay firmware package, published on 24 Jun 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-1667 in the wild and no public exploit code.\n\nAffected product: Secheron SEPCOS Control and Protection Relay firmware package. 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-1667/ (Markdown: https://insights.sbomify.com/CVE-2022-1667/index.md)","id":"CVE-2022-1667","markdown":"https://insights.sbomify.com/CVE-2022-1667/index.md","name":"CVE-2022-1667","record":{"aliases":["GHSA-mvc4-c2h4-573v"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Control and Protection Relay","requires_auth":"none","summary":"Attackers can bypass client-side controls to reboot the relay by directly accessing backend scripts or executing JavaScript functions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"sepcos_control_and_protection_relay_firmware","vendor":"secheron"}],"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-841","name":"Improper Enforcement of Behavioral Workflow"}],"description":"Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the browser console) or by loading the corresponding, browser accessible PHP script","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":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-1667","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-1668"},"packages":[],"prev":{"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-1666"},"products":["SEPCOS Control and Protection Relay firmware package"],"published":"2022-06-24","related":[{"cvss_score":9.9,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-2104","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":9.8,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-1668","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":9.8,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-2103","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":9.4,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-2102","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":9.4,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-2105","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":6.5,"headline":"Secheron SEPCOS Control and Protection Relay","id":"CVE-2022-1666","kev_date_added":null,"published":"2022-06-24"}],"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-04-16","vendors":["Secheron"]},"summary":"Attackers can bypass client-side controls to reboot the relay by directly accessing backend scripts or executing JavaScript functions.","url":"https://insights.sbomify.com/CVE-2022-1667/"}