{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-30318 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30318 is a critical vulnerability in n/a, published on 31 Aug 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-30318 and fix it if it is affected.\n\nWhat it is: CVE-2022-30318 is a critical vulnerability in n/a, published on 31 Aug 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-30318 in the wild and no public exploit code.\n\nAffected product: n/a. 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-30318/ (Markdown: https://insights.sbomify.com/CVE-2022-30318/index.md)","id":"CVE-2022-30318","markdown":"https://insights.sbomify.com/CVE-2022-30318/index.md","name":"CVE-2022-30318","record":{"aliases":["GHSA-2jhj-7g8h-j3h6"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Honeywell ControlEdge PLC/RTU","requires_auth":"none","summary":"Hardcoded root SSH credentials in Honeywell ControlEdge PLC/RTU firmware allow attackers to gain root access, execute code, and disrupt operations.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"controledge_plc_firmware","vendor":"honeywell"},{"product":"controledge_rtu_firmware","vendor":"honeywell"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Honeywell ControlEdge through R151.1 uses Hard-coded Credentials. According to FSCT-2022-0056, there is a Honeywell ControlEdge hardcoded credentials issue. The affected components are characterized as: SSH. The potential impact is: Remote code execution, manipulate configuration, denial of service. The Honeywell ControlEdge PLC and RTU product line exposes an SSH service on port 22/TCP. Login as root to this service is permitted and credentials for the root user are hardcoded without automatically changing them upon first commissioning. The credentials for the SSH service are hardcoded in the firmware. The credentials grant an attacker access to a root shell on the PLC/RTU, allowing for remote code execution, configuration manipulation and denial of service.","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":"Hardcoded credentials in n/a","id":"CVE-2022-30318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-30319"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-30317"},"products":["n/a"],"published":"2022-08-31","related":[{"cvss_score":7.5,"headline":"Information disclosure in ControlEdge PLC","id":"CVE-2020-10624","kev_date_added":null,"published":"2020-06-26"},{"cvss_score":7.5,"headline":"Information disclosure in ControlEdge PLC","id":"CVE-2020-10628","kev_date_added":null,"published":"2020-06-26"}],"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":["n/a"]},"summary":"Hardcoded root SSH credentials in Honeywell ControlEdge PLC/RTU firmware allow attackers to gain root access, execute code, and disrupt operations.","url":"https://insights.sbomify.com/CVE-2022-30318/"}