The Emerson ROC and FloBoss RTU product lines through 2022-05-02 perform insecure filesystem operations.

published 2022-08-16 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52223

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

emerson roc809_firmware 2022-05-02
emerson roc827_firmware 2022-05-02

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-223-04 updated 2022-08-11 cvss 6.3

Emerson ROC800, ROC800L and DL8000

Emerson DL8000 Emerson ROC800 Emerson ROC800L
affected: mitigation “Emerson recommends users follow the guidance given in the ROC800-Series Remote Operations Controller Instruction Manual under section 1.11 Secure Gateway D301766X012” emerson.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

forescout.com /blog/
third-party-advisory
cisa.gov /uscert/ics/advisories/icsa-22-223-04
mitigation, third-party-advisory, us-government-resource

Sources

CVE List CVE-2022-30264
NVD CVE-2022-30264

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary