# CVE-2019-10688: Hardcoded credentials in n/a

> Hard-coded credentials in Polycom VVX phones allow attackers to bypass authentication and take over device connections.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vv4j-2mxx-3j2j

## What is CVE-2019-10688?

CVE-2019-10688 is a medium-severity vulnerability in n/a, published on 23 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VVX products with software versions including and prior to, UCS 5.9.2 with Better Together over Ethernet Connector (BToE) application 3.9.1, use hard-coded credentials to establish connections between the host application and the device.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2019-10688?

It affects 2 products.


Products: Polycom Better Together Over Ethernet Connector, Polycom Unified Communications Software.

## How do I fix CVE-2019-10688?

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

## Is CVE-2019-10688 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10689](https://insights.sbomify.com/CVE-2019-10689/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10688 and fix it if it is affected.

What it is: CVE-2019-10688 is a medium-severity vulnerability in n/a, published on 23 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10688 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-2019-10688/ (Markdown: https://insights.sbomify.com/CVE-2019-10688/index.md)
```

## Sources

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

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