CVE-2018-10633 json
Universal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100 utilizes hard-coded credentials that may allow an attacker to reset…
published 8y ago modified 4mo ago also EUVD-2018-2705
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Universal Robots Robot Controllers Version CB 3.1, SW Version 3.4.5-100 utilizes hard-coded credentials that may allow an attacker to reset passwords for the controller.
Is CVE-2018-10633 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-191-01 updated cvss 7.3
Universal Robots Robot Controllers
-
Universal Robots CB 3.1 SW 3.4.5-100affected: mitigation “Only allow trusted users physical access to the robot control box and teach pendant.”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Universal Robots Universal Robots Robot Controller version CB 3.1, SW Version 3.4.5-100
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
securityfocus.com
/bid/104710
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-191-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2018-10633
- NVD CVE-2018-10633
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.