CVE-2022-30264
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Emerson ROC and FloBoss RTU product lines contain a vulnerability in the ROC protocol (ports 4000/TCP, 5000/TCP) where Opcode 203 allows a remote attacker to perform arbitrary file and directory read, write, and delete operations on the device's flash filesystem. This enables complete compromise of the RTU firmware and configuration through insecure filesystem operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2022-05-02< 2022-05-02<= 2022-05-02<= 2022-05-02< 2022-05-02CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web interface, console, or management interface and locate the model information (Dl8000, Roc809, Roc800l, Fb3000, or Roc827).Affected if The device is one of these models and has not been patched to a version released after 2022-05-02.
-
Check the firmware versionLocate the firmware version information in the device's web interface, console, or management interface. Compare it to the affected version thresholds: <= 2022-05-02 for Dl8000, Roc800l, Fb327; < 2022-05-02 for Roc809, Roc827.Affected if The installed firmware version is at or before 2022-05-02.
-
Verify ROC protocol ports are accessibleScan the device or firewall logs for open ports 4000/TCP and 5000/TCP using a network scanner or by checking the device's port listening status.Affected if Ports 4000/TCP or 5000/TCP are open and reachable from an untrusted network segment.
-
Confirm ROC protocol is enabledCheck the device configuration to confirm that the ROC protocol service is enabled and accepting connections on ports 4000/TCP or 5000/TCP.Affected if The ROC protocol is enabled and accessible on the network.
A user is affected if the device is an Emerson Dl8000, Roc809, Roc800l, Fb3000, or Roc827 running firmware at or before 2022-05-02, and the ROC protocol on ports 4000/TCP or 5000/TCP is enabled and reachable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2022-05-02
Restrict network access to ports 4000/TCP and 5000/TCP using network segmentation and firewalls to limit exposure to trusted hosts only. If available, apply vendor-supplied patches and coordinate with Emerson for firmware updates.
- Consultation12.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30264 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data