CVE-2023-1935
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 · uneditedROC800-Series RTU devices are vulnerable to an authentication bypass, which could allow an attacker to gain unauthorized access to data or control of the device and cause a denial-of-service condition.
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 · moderate confidenceThe ROC800-Series RTU devices contain an authentication bypass vulnerability that allows unauthenticated attackers to gain unauthorized access to device data or control functionality. This critical flaw can also be exploited to cause a denial-of-service condition on the affected devices.
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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 device modelAccess the device management interface or check device labeling/documentation to confirm the exact model number (Roc809, Roc827, Roc809l, Roc827l, or Dl8000)Affected if The device model is any of: Roc809, Roc827, Roc809l, Roc827l, or Dl8000
-
Confirm firmware versionCheck the device firmware version through its web interface, console, or management software. Look for a version string in the device status or system information section.Affected if All firmware versions are affected - no version provides immunity
-
Assess network exposureReview network firewall rules, ACLs, and device IP assignments to determine if the ROC device management ports (HTTP/HTTPS, Telnet, SNMP, OT protocols like Modbus/DNP3) are accessible from untrusted networks or the internetAffected if The device management or OT protocol ports are reachable from untrusted networks without proper network segmentation
-
Check for direct internet connectivityPerform a reverse DNS lookup or check routing tables to see if the device has a public IP address or is behind insufficiently restrictive perimeter securityAffected if The device has a public IP address or is accessible via inadequate NAT/firewall rules from external networks
If the device is any model in the ROC800-Series or DL8000 family and its management/OT ports are accessible from untrusted networks, the environment is vulnerable to unauthenticated access and should be segmented immediately.
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 dataApply vendor-provided patches/firmware updates for the ROC800-Series when available, implement network segmentation to isolate OT devices from untrusted networks, and enforce strict access controls.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1935 — 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-2023-1935 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