# CVE-2017-16666: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in uploaded PCAP filenames, potentially leading to full system compromise.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2w2r-jcr9-2rp9

## What is CVE-2017-16666?

CVE-2017-16666 is a high-severity command injection vulnerability in n/a, published on 5 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xplico before 1.2.1 allows remote authenticated users to execute arbitrary commands via shell metacharacters in the name of an uploaded PCAP file.  NOTE: this issue can be exploited without authentication by leveraging the user registration feature.

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

## Which versions are affected by CVE-2017-16666?

It affects 1 product.


Products: Xplico Xplico.

## How do I fix CVE-2017-16666?

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

## Is CVE-2017-16666 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16666 exists.

Public exploit code:

- Xplico Remote Code Execution (metasploit)
- Xplico - Remote Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16666 and fix it if it is affected.

What it is: CVE-2017-16666 is a high-severity command injection vulnerability in n/a, published on 5 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16666 exists.

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-2017-16666/ (Markdown: https://insights.sbomify.com/CVE-2017-16666/index.md)
```

## Sources

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

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