# CVE-2018-17931: Privilege escalation in VGo Robot

> An attacker with physical access can alter scripts to execute code with root privileges on the VGo Robot.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v335-f4p4-hmpj

## What is CVE-2018-17931?

CVE-2018-17931 is a medium-severity vulnerability in VGo Robot, published on 30 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2018-17931?

It affects 1 product.


Products: Vecna Vgo Firmware.

## How do I fix CVE-2018-17931?

No fix has been published for CVE-2018-17931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-17931 being exploited?

There is no known exploitation of CVE-2018-17931 in the wild and no public exploit code.

## Other vulnerabilities in VGo Robot

- [CVE-2018-8858](https://insights.sbomify.com/CVE-2018-8858/): Hardcoded credentials in VGo Robot (critical 9.8)
- [CVE-2018-17933](https://insights.sbomify.com/CVE-2018-17933/): Privilege escalation in VGo Robot (high 8.8)
- [CVE-2018-8866](https://insights.sbomify.com/CVE-2018-8866/): Command injection in VGo Robot (high 8.8)
- [CVE-2018-8860](https://insights.sbomify.com/CVE-2018-8860/): Information disclosure in VGo Robot (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17931 and fix it if it is affected.

What it is: CVE-2018-17931 is a medium-severity vulnerability in VGo Robot, published on 30 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17931 in the wild and no public exploit code.

Affected product: VGo Robot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-17931/ (Markdown: https://insights.sbomify.com/CVE-2018-17931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-17931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-17931
- OSV: https://osv.dev/vulnerability/CVE-2018-17931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-17931/
Summaries are generated and may contain mistakes; the official description above is the record.