CVE-2018-17931
No exploitation reported by the sources we read.
- Published2018-10-30
- WeaknessCWE-284
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
If an attacker has physical access to the VGo Robot (Versions 3.0.3.52164 and 3.0.3.53662. Prior versions may also be affected) they may be able to alter scripts, which may allow code execution with root privileges.
Timeline
dates in UTC- 2018-10-3021:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-17931?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-17931?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.0 | ≤ 3.0.3.52164 | no fix published | NVD |
| 3.0 | = 3.0.3.53662 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Vecna VGo Robot (Update A)
Go Robot: Versions 3.0.3.52164 and 3.0.3.53662. Prior versions may also be affected
Fix
- Mitigation from the vendor CISA ICSA-18-114-01 · 1 productBy default, VGo has automatic updates enabled so all updates are performed automatically when Internet access is available. If the VGo is powered off or in use, a message will appear on the screen asking if it can be updated when the VGo is next used.
- Mitigation from the vendor CISA ICSA-18-114-01 · 1 productIf a VGo unit has automatic updates turned off, the update will not be downloaded (however, a notice about the update will be displayed on the VGo's screen). Vecna recommends that automatic updates be turned on. Select “settings” from the main menu then “advanced settings” then “automatic updates.”
- Mitigation from the vendor CISA ICSA-18-114-01 · 1 productVecna has not addressed CVE-2018-17931 and CVE-2018-17933.
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.06.8read 2026-10-23
- NVDCVSS 2.07.2read 2026-10-23
- CNAweakness (CWE)CWE-284read 2026-10-23
- NVDweakness (CWE)CWE-284read 2026-10-23
- FIRST EPSSEPSS score0.4 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-10-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-17931?
Is CVE-2018-17931 actively exploited?
What is the CVSS score for CVE-2018-17931?
Running Vecna VGo Robot? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.