# CVE-2022-30319: Auth bypass in n/a

> Attackers can spoof UDP traffic to bypass MAC/IP whitelists, gaining unauthorized access to modify control logic and configuration on SBC PCD controllers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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:** 20 Nov 2024
- **Also known as:** GHSA-vqj4-mpgw-jrqv

## What is CVE-2022-30319?

CVE-2022-30319 is a high-severity authentication bypass 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

Saia Burgess Controls (SBC) PCD through 2022-05-06 allows Authentication bypass. According to FSCT-2022-0062, there is a Saia Burgess Controls (SBC) PCD S-Bus authentication bypass issue. The affected components are characterized as: S-Bus (5050/UDP) authentication. The potential impact is: Authentication bypass. The Saia Burgess Controls (SBC) PCD controllers utilize the S-Bus protocol (5050/UDP) for a variety of engineering purposes. It is possible to configure a password in order to restrict access to sensitive engineering functionality. Authentication functions on the basis of a MAC/IP whitelist with inactivity timeout to which an authenticated client's MAC/IP is stored. UDP traffic can be spoofed to bypass the whitelist-based access control. Since UDP is stateless, an attacker capable of passively observing traffic can spoof arbitrary messages using the MAC/IP of an authenticated client. This allows the attacker access to sensitive engineering functionality such as uploading/downloading control logic and manipulating controller configuration.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Honeywell Saia Pg5 Controls Suite.

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

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

## Is CVE-2022-30319 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51599](https://insights.sbomify.com/CVE-2023-51599/): Honeywell Saia PG5 Controls Suite Directory Traversal Remote Code Execution Vulnerability (high 7.8)
- [CVE-2023-51603](https://insights.sbomify.com/CVE-2023-51603/): Honeywell Saia PG5 Controls Suite CAB File Parsing Directory Traversal Remote Code Execution Vulnerability (high 7.8)
- [CVE-2023-51600](https://insights.sbomify.com/CVE-2023-51600/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)
- [CVE-2023-51601](https://insights.sbomify.com/CVE-2023-51601/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)
- [CVE-2023-51602](https://insights.sbomify.com/CVE-2023-51602/): Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30319 is a high-severity authentication bypass 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-30319 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-30319/ (Markdown: https://insights.sbomify.com/CVE-2022-30319/index.md)
```

## Sources

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

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