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

> Attackers can bypass firmware integrity checks in Emerson DeltaV systems to execute malicious code due to inadequate checksums and missing signatures.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xc7c-c2g3-58v4

## What is CVE-2022-30260?

CVE-2022-30260 is a high-severity vulnerability in n/a, published on 26 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Emerson DeltaV Distributed Control System (DCS) has insufficient verification of firmware integrity (an inadequate checksum approach, and no signature). This affects versions before 14.3 of DeltaV M-series, DeltaV S-series, DeltaV P-series, DeltaV SIS, and DeltaV CIOC/EIOC/WIOC IO cards.

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

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

It affects 24 products.


Products: Emerson Deltav Distributed Control System Sq Controller Firmware, Emerson Deltav Distributed Control System Sx Controller Firmware, Emerson Se4002s1t2b6 High Side 40-Pin Mass I\/O Terminal Block Firmware, Emerson Se4003s2b4 16-Pin Mass I\/O Terminal Block Firmware, Emerson Se4003s2b524-Pin Mass I\/O Terminal Block Firmware, Emerson Se4017p0 H1 I\/O Interface Card and Terminl Block Firmware, Emerson Se4017p1 H1 I\/O Card With Integrated Power Firmware, Emerson Se4019p0 Simplex H1 4-Port Plus Fieldbus I\/O Interface With Terminalblock Firmware, Emerson Se4026 Virtual I\/O Module 2 Firmware, Emerson Se4027 Virtual I\/O Module 2 Firmware, Emerson Se4032s1t2b8 High Side 40-Pin Do Mass I\/O Terminal Block Firmware, Emerson Se4037p0 H1 I\/O Interface Card and Terminl Block Firmware, Emerson Se4037p1 Redundant H1 I\/O Card With Integrated Power and Terminal Block Firmware, Emerson Se4039p0 Redundant H1 4-Port Plus Fieldbus I\/O Interface With Terminalblock Firmware, Emerson Se4052s1t2b6 High Side 40-Pin Mass I\/O Terminal Block Firmware, Emerson Se4082s1t2b8 High Side 40-Pin Do Mass I\/O Terminal Block Firmware, Emerson Se4100 Simplex Ethernet I\/O Card \(Eioc\) Assembly Firmware, Emerson Se4101 Simplex Ethernet I\/O Card \(Eioc\) Assembly Firmware, Emerson Se4801t0x Redundant Wireless I\/O Card Firmware, Emerson Ve4103 Modbus Tcp Interface for Ethernet Connected I\/O \(Eioc\) Firmware and 4 more.

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

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

## Is CVE-2022-30260 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29962](https://insights.sbomify.com/CVE-2022-29962/): Hardcoded credentials in n/a (medium 5.5)
- [CVE-2022-29963](https://insights.sbomify.com/CVE-2022-29963/): Hardcoded credentials in n/a (medium 5.5)
- [CVE-2022-29964](https://insights.sbomify.com/CVE-2022-29964/): Hardcoded credentials in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30260 is a high-severity vulnerability in n/a, published on 26 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-30260 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-30260/ (Markdown: https://insights.sbomify.com/CVE-2022-30260/index.md)
```

## Sources

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

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