# CVE-2022-30314: Hardcoded credentials in n/a

> Hardcoded credentials in the POLO bootloader allow attackers with serial access to manipulate firmware and control the boot process.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4g4w-x2j6-rp8q

## What is CVE-2022-30314?

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.

### Official 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).

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-30314?

It affects 1 product.


Products: Honeywell Safety Manager Firmware.

## How do I fix CVE-2022-30314?

No fix has been published for CVE-2022-30314 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-30314 being exploited?

There is no known exploitation of CVE-2022-30314 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-30315](https://insights.sbomify.com/CVE-2022-30315/): Code injection in n/a (critical 9.8)
- [CVE-2022-30313](https://insights.sbomify.com/CVE-2022-30313/): Missing authorization in n/a (high 7.5)
- [CVE-2022-30316](https://insights.sbomify.com/CVE-2022-30316/): Missing authorization in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30314 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2022-30314 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-30314/ (Markdown: https://insights.sbomify.com/CVE-2022-30314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30314
- OSV: https://osv.dev/vulnerability/CVE-2022-30314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-30314/
Summaries are generated and may contain mistakes; the official description above is the record.