{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30314 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30314 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30314 is a medium-severity vulnerability in n/a, published on 28 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30314 and fix it if it is affected.\n\nWhat it is: CVE-2022-30314 is a medium-severity vulnerability in n/a, published on 28 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-30314 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-30314/ (Markdown: https://insights.sbomify.com/CVE-2022-30314/index.md)","id":"CVE-2022-30314","markdown":"https://insights.sbomify.com/CVE-2022-30314/index.md","name":"CVE-2022-30314","record":{"aliases":["GHSA-4g4w-x2j6-rp8q"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Honeywell Experion PKS","requires_auth":"none","summary":"Hardcoded credentials in the POLO bootloader allow attackers with serial access to manipulate firmware and control the boot process.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"safety_manager_firmware","vendor":"honeywell"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Honeywell Experion PKS Safety Manager 5.02 uses Hard-coded Credentials. According to FSCT-2022-0052, there is a Honeywell Experion PKS Safety Manager hardcoded credentials issue. The affected components are characterized as: POLO bootloader. The potential impact is: Manipulate firmware. The Honeywell Experion PKS Safety Manager utilizes the DCOM-232/485 serial interface for firmware management purposes. When booting, the Safety Manager exposes the Enea POLO bootloader via this interface. Access to the boot configuration is controlled by means of credentials hardcoded in the Safety Manager firmware. The credentials for the bootloader are hardcoded in the firmware. An attacker with access to the serial interface (either through physical access, a compromised EWS or an exposed serial-to-ethernet gateway) can utilize these credentials to control the boot process and manipulate the unauthenticated firmware image (see FSCT-2022-0054).","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-30314","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":"Code injection in n/a","id":"CVE-2022-30315"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-30313"},"products":["n/a"],"published":"2022-07-28","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-30315","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-30313","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":6.8,"headline":"Missing authorization in n/a","id":"CVE-2022-30316","kev_date_added":null,"published":"2022-07-28"}],"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 credentials in the POLO bootloader allow attackers with serial access to manipulate firmware and control the boot process.","url":"https://insights.sbomify.com/CVE-2022-30314/"}