dbcve.org
Cb3.1 FirmwareOperating system · Universal Robots

CVE-2018-10635

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Universal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100, ports 30001/TCP to 30003/TCP listen for arbitrary URScript code and execute the code. This enables a remote attacker who has access to the ports to remotely execute code that may allow root access to be obtained.

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 confidence

Unauthenticated remote code execution vulnerability in Universal Robots CB 3.1 controllers running SW 3.4.5-100. TCP ports 30001-30003 accept arbitrary URScript commands and execute them without authentication, potentially with root privileges, allowing complete compromise of the robot controller.

MitigationIsolate robot controllers on a restricted VLAN with firewall rules blocking unauthorized access to ports 30001-30003; if the URScript interface is not required for operations, disable it or apply vendor patches.

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
Cb3.1 FirmwareOperating system
Affected:= 3.4.5-100

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify firmware version
    Access the robot controller's web interface or use the PolyScope HMI to navigate to Settings > System > About. Alternatively, connect to the controller via SSH and run 'cat /etc/version' or check the 'urcontrol.conf' file.
    Affected if The firmware version is exactly 3.4.5-100
  2. Verify TCP ports 30001-30003 are listening
    From a network-connected host, run 'nmap -p 30001,30002,30003 <controller_ip>' or use 'netstat -an | grep 3000' on the controller itself to confirm the ports are in LISTEN state.
    Affected if One or more of ports 30001, 30002, or 30003 are open and accepting connections
  3. Confirm URScript interface accepts unauthenticated commands
    Send a simple URScript command (e.g., 'textmsg("test")') via netcat or Python socket to port 30001 without providing any credentials: 'echo "textmsg(\"test\")" | nc <controller_ip> 30001'.
    Affected if The command executes and returns a response without requiring authentication
  4. Check network accessibility of controller ports
    Attempt an outbound TCP connection to ports 30001-30003 from an untrusted network segment. Use 'telnet <controller_ip> 30001' or 'nc -zv <controller_ip> 30001-30003'.
    Affected if The ports are reachable from a network outside the intended operational VLAN
  5. Verify no authentication mechanism is enforced
    Review the controller's network security settings via the web dashboard or PolyScope under Settings > Network > Remote Control. Confirm that 'Authentication required' is not enabled for the Dashboard server on ports 29999-30001.
    Affected if Remote URScript execution is enabled without authentication enforcement

A system is affected if it is a Universal Robots CB 3.1 controller running firmware version 3.4.5-100 with TCP ports 30001-30003 accessible and the URScript interface accepting unauthenticated commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate robot controllers on a restricted VLAN with firewall rules blocking unauthorized access to ports 30001-30003; if the URScript interface is not required for operations, disable it or apply vendor patches.

Recommended fix Moderate confidence

Universal Robots CB series firmware version with authentication enabled (contact vendor for specific version)

  1. Identify all Universal Robots CB 3.1 controllers running SW version 3.4.5-100 on the network
  2. Verify network accessibility to ports 30001/TCP, 30002/30003 on affected devices
  3. Restrict network access to ports 30001-30003 using firewall rules or network segmentation to prevent unauthorized external access
  4. Contact Universal Robots for the latest firmware version that addresses CVE-2018-10635
  5. Schedule maintenance window for firmware upgrade
  6. After upgrade, verify that authentication is required for URScript execution on ports 30001-30003
  7. Confirm ports are no longer accessible from untrusted networks
Caveat Firmware upgrade may require validation of existing programs and safety configurations; test thoroughly in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cb3.1 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10635 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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