dbcve.org
Ur SoftwareApplication · Universal Robots

CVE-2020-10264

HIGH · 8.8 CVSS v3.1 Published 2020-04-06
Fix available
A fix is available. Upgrade to after 3.3.3.292 or later.
See remediation →
93/100
Remediation priority · Urgent
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
CB3 SW Version 3.3 and upwards, e-series SW Version 5.0 and upwards allow authenticated access to the RTDE (Real-Time Data Exchange) interface on port 30004 which allows setting registers, the speed slider fraction as well as digital and analog Outputs. Additionally unautheticated reading of robot data is also possible

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

The RTDE (Real-Time Data Exchange) interface on Universal Robots CB3 (v3.3+) and e-series (v5.0+) controllers exposes port 30004 with two distinct issues: authenticated users can write to registers, speed slider, and digital/analog outputs (enabling manipulation of robot behavior), while unauthenticated attackers can read robot telemetry data for reconnaissance.

MitigationIsolate robot controllers on a restricted VLAN, block unauthorized access to port 30004 at the network perimeter, disable RTDE if not required, or implement IP-based access control lists; verify all accounts use strong authentication if RTDE authentication is needed.

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
Ur SoftwareApplication
Affected:>= 3.0.14989, <= 3.3.3.292>= 5.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 the Universal Robots controller software version
    Access the robot controller's Teach Pendant, go to 'About' or 'System' settings, and note the installed software version. Alternatively, check the robot's web interface or use the urscripts API call get_controller_version().
    Affected if The installed version is >= 3.0.14989 and <= 3.3.3.292, or >= 5.0.
  2. Verify if RTDE interface is enabled
    Check if port 30004 is listening on the controller. From a connected machine, run 'nc -zv <robot_ip> 30004' or use a port scanner. In the robot's web UI, navigate to 'Settings' > 'RTDE' to see if the interface is enabled.
    Affected if Port 30004 is open and accepting connections, indicating RTDE is active.
  3. Confirm network accessibility to RTDE port
    Review firewall rules, VLAN configuration, and network segmentation. Check if port 30004 is accessible from network segments that contain untrusted devices or the internet. Use 'nmap -p 30004 <robot_ip>' to verify port status from external locations.
    Affected if Port 30004 is reachable from untrusted network segments or directly from the internet.
  4. Determine if RTDE authentication is enforced
    Attempt to connect to RTDE without credentials using a script or tool like the rtde Python library. Check the RTDE configuration in the robot's web interface under 'Settings' > 'RTDE' to see if 'Authentication Required' is enabled.
    Affected if RTDE accepts connections without requiring authentication credentials.

Your environment is affected if the controller runs software version 3.0.14989-3.3.3.292 or >=5.0, the RTDE interface on port 30004 is enabled and accessible from your network, and no authentication is required for RTDE connections.

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.

From vendor data
Upgrade available Upgrade to a release after 3.3.3.292
Interim mitigation

Isolate robot controllers on a restricted VLAN, block unauthorized access to port 30004 at the network perimeter, disable RTDE if not required, or implement IP-based access control lists; verify all accounts use strong authentication if RTDE authentication is needed.

Fix this in Ur Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10264 — 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-2020-10264 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