# CVE-2022-30262: Security feature bypass in n/a

> Attackers can bypass firmware integrity checks to install malicious firmware on Emerson ControlWave RTUs due to lack of signing.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g3xq-mfm7-v29h

## What is CVE-2022-30262?

CVE-2022-30262 is a high-severity vulnerability in n/a, published on 17 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Emerson ControlWave 'Next Generation' RTUs through 2022-05-02 mishandle firmware integrity. They utilize the BSAP-IP protocol to transmit firmware updates. Firmware updates are supplied as CAB archive files containing a binary firmware image. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 2 products.


Products: Emerson Controlwave Micro Firmware, Emerson Controlwave Pac Firmware.

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

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

## Is CVE-2022-30262 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5452](https://insights.sbomify.com/CVE-2018-5452/): Memory corruption in Emerson ControlWave Micro Process Automation Controller (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30262 is a high-severity vulnerability in n/a, published on 17 Aug 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-30262 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-30262/ (Markdown: https://insights.sbomify.com/CVE-2022-30262/index.md)
```

## Sources

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

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