LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10635: In Universal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100, ports 30001/TCP to 30003/TCP li...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw means an affected Universal Robots controller can accept and run robot script instructions sent over specific network ports without authentication. If those ports are reachable, an attacker could change controller behavior and potentially gain deeper system access. Business urgency depends on whether affected controllers are deployed and reachable from untrusted networks. Likely exposure is limited to Universal Robots CB 3.1 controllers running SW Version 3.4.5-100 with TCP 30001-30003 reachable. The source bundle does not identify other affected products or versions. Exposure rises sharply if plant networks, remote access services, or broader corporate networks can reach those ports. Prioritize if affected robots are in production or reachable beyond a tightly controlled engineering network. The issue can allow remote code execution on industrial equipment, so exposure could affect safety, operations, and uptime. If no affected version or port exposure exists, track as a documented exception. Mitigation focus: Check Universal Robots and CISA ICS-CERT guidance for supported fixes or compensating controls.; Restrict TCP 30001-30003 to only explicitly trusted engineering hosts.; Isolate affected robot controllers from corporate and internet-reachable networks..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-10635 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Universal RobotsUniversal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100Universal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.