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

> Remote authenticated attackers can execute arbitrary commands on Poly Trio IP phones via the ping command, leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 28 Dec 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-68wq-r372-q8gf

## What is CVE-2018-17875?

CVE-2018-17875 is a high-severity command injection vulnerability in n/a, published on 28 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A remote code execution issue in the ping command on Poly Trio 8800 5.7.1.4145 devices allows remote authenticated users to execute commands via unspecified vectors.

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

It affects 1 product.


Products: Poly Trio 8800 Firmware.

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

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

## Is CVE-2018-17875 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-4467](https://insights.sbomify.com/CVE-2023-4467/): Poly Trio 8800 Test Automation Mode backdoor (medium 6.2)
- [CVE-2023-24282](https://insights.sbomify.com/CVE-2023-24282/): File upload in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17875 is a high-severity command injection vulnerability in n/a, published on 28 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17875 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-17875/ (Markdown: https://insights.sbomify.com/CVE-2018-17875/index.md)
```

## Sources

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

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