# CVE-2022-30264: Path traversal in n/a

> Attackers can read, write, or delete arbitrary files on Emerson ROC and FloBoss RTUs via insecure filesystem operations in the ROC protocol.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hr3f-j6vx-grx5

## What is CVE-2022-30264?

CVE-2022-30264 is a critical path traversal vulnerability in n/a, published on 16 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Emerson ROC and FloBoss RTU product lines through 2022-05-02 perform insecure filesystem operations. They utilize the ROC protocol (4000/TCP, 5000/TCP) for communications between a master terminal and RTUs. Opcode 203 of this protocol allows a master terminal to transfer files to and from the flash filesystem and carrying out arbitrary file and directory read, write, and delete operations.

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

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

It affects 5 products.


Products: Emerson Dl8000 Firmware, Emerson Fb3000 Rtu Firmware, Emerson Roc800l Firmware, Emerson Roc809 Firmware, Emerson Roc827 Firmware.

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

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

## Is CVE-2022-30264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-1935](https://insights.sbomify.com/CVE-2023-1935/): CVE-2023-1935 (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30264 is a critical path traversal vulnerability in n/a, published on 16 Aug 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-30264 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-30264/ (Markdown: https://insights.sbomify.com/CVE-2022-30264/index.md)
```

## Sources

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

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