# CVE-2022-30313: Missing authorization in n/a

> Unauthenticated access to Honeywell Experion PKS Safety Manager protocols allows attackers to manipulate controller state, configuration, and logic.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2022
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-qr79-94p4-h8hm

## What is CVE-2022-30313?

CVE-2022-30313 is a high-severity missing authorization vulnerability in n/a, published on 28 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Honeywell Experion PKS Safety Manager through 2022-05-06 has Missing Authentication for a Critical Function. According to FSCT-2022-0051, there is a Honeywell Experion PKS Safety Manager multiple proprietary protocols with unauthenticated functionality issue. The affected components are characterized as: Honeywell Experion TCP (51000/TCP), Safety Builder (51010/TCP). The potential impact is: Manipulate controller state, Manipulate controller configuration, Manipulate controller logic, Manipulate controller files, Manipulate IO. The Honeywell Experion PKS Distributed Control System (DCS) Safety Manager utilizes several proprietary protocols for a wide variety of functionality, including process data acquisition, controller steering and configuration management. These protocols include: Experion TCP (51000/TCP) and Safety Builder (51010/TCP). None of these protocols have any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality. There is no authentication functionality on the protocols in question. An attacker capable of invoking the protocols' functionalities could achieve a wide range of adverse impacts, including (but not limited to), the following: for Experion TCP (51000/TCP): Issue IO manipulation commands, Issue file read/write commands; and for Safety Builder (51010/TCP): Issue controller start/stop commands, Issue logic download/upload commands, Issue file read commands, Issue system time change commands. A mitigating factor with regards to some, but not all, of the above functionality is that these require the Safety Manager physical keyswitch to be in the right position.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Honeywell Safety Manager Firmware.

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

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

## Is CVE-2022-30313 being exploited?

There is no known exploitation of CVE-2022-30313 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-30316](https://insights.sbomify.com/CVE-2022-30316/): Missing authorization in n/a (medium 6.8)
- [CVE-2022-30314](https://insights.sbomify.com/CVE-2022-30314/): Hardcoded credentials in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30313 is a high-severity missing authorization vulnerability in n/a, published on 28 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30313 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-30313/ (Markdown: https://insights.sbomify.com/CVE-2022-30313/index.md)
```

## Sources

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

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