# CVE-2017-12857: Information disclosure in n/a

> Authenticated attackers can read phone memory to expose administrator passwords and sensitive data on Polycom IP phones.

- **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:** 25 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-66pc-jh3g-9256

## What is CVE-2017-12857?

CVE-2017-12857 is a high-severity vulnerability in n/a, published on 25 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Polycom SoundStation IP, VVX, and RealPresence Trio that are running software older than UCS 4.0.12, 5.4.5 rev AG, 5.4.7, 5.5.2, or 5.6.0 are affected by a vulnerability in their UCS web application. This vulnerability could allow an authenticated remote attacker to read a segment of the phone's memory which could contain an administrator's password or other sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Polycom Unified Communications Software.

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

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

## Is CVE-2017-12857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12948](https://insights.sbomify.com/CVE-2019-12948/): Code injection in n/a (high 8.3)
- [CVE-2018-18568](https://insights.sbomify.com/CVE-2018-18568/): Weak cryptography in n/a (medium 5.9)
- [CVE-2018-18566](https://insights.sbomify.com/CVE-2018-18566/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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