# CVE-2018-16618: Command injection in n/a

> Remote attackers can execute arbitrary commands as root on VTech Storio Max devices by injecting shell metacharacters into Android activity names via a local service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jpcr-xvwv-ch4p

## What is CVE-2018-16618?

CVE-2018-16618 is a critical command injection vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VTech Storio Max before 56.D3JM6 allows remote command execution via shell metacharacters in an Android activity name. It exposes the storeintenttranslate.x service on port 1668 listening for requests on localhost. Requests submitted to this service are checked for a string of random characters followed by the name of an Android activity to start. Activities are started by inserting their name into a string that is executed in a shell command. By inserting metacharacters this can be exploited to run arbitrary commands as root. The requests also match those of the HTTP protocol and can be triggered on any web page rendered on the device by requesting resources stored at an http://127.0.0.1:1668/ URI, as demonstrated by the http://127.0.0.1:1668/dacdb70556479813fab2d92896596eef?';{ping,example.org}' URL.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Vtech Storio Max Firmware.

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

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

## Is CVE-2018-16618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16618 is a critical command injection vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16618 in the wild and no public exploit code.

Affected product: n/a. 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-16618/ (Markdown: https://insights.sbomify.com/CVE-2018-16618/index.md)
```

## Sources

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

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