# CVE-2012-6610: Command injection in n/a

> Remote authenticated users can execute arbitrary commands on Polycom HDX and UC APL devices via the ping feature.

- **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 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8gv2-j7j8-vrh8

## What is CVE-2012-6610?

CVE-2012-6610 is a high-severity command injection vulnerability in n/a, published on 28 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Polycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J allows remote authenticated users to execute arbitrary commands as demonstrated by a ; (semicolon) to the ping command feature.

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

## Which versions are affected by CVE-2012-6610?

It affects 2 products.


Products: Polycom Hdx Video End Points, Polycom Uc Apl.

## How do I fix CVE-2012-6610?

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

## Is CVE-2012-6610 being exploited?

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

Public exploit code:

- Polycom Command Shell Authorization Bypass (metasploit)

## Other vulnerabilities in n/a

- [CVE-2012-6609](https://insights.sbomify.com/CVE-2012-6609/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6610 and fix it if it is affected.

What it is: CVE-2012-6610 is a high-severity command injection vulnerability in n/a, published on 28 Jan 2020. 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-2012-6610 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-2012-6610/ (Markdown: https://insights.sbomify.com/CVE-2012-6610/index.md)
```

## Sources

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

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