CVE-2017-12857
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPolycom 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory disclosure vulnerability in the UCS web application of Polycom SoundStation IP, VVX, and RealPresence Trio phones. An authenticated attacker can read arbitrary memory segments, potentially exposing administrator credentials or other sensitive data stored in memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.0.11<= 5.4.6<= 5.5.1<= 5.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Polycom phone models in your environmentInventory your network devices or check the physical devices for model numbers (SoundStation IP, VVX series, or RealPresence Trio)Affected if Any of these three model families are present in your environment
-
Check installed UCS firmware versionAccess the phone web interface or admin console and navigate to Status > System Information, or use the SIP invite payload to query the software version. Compare against affected ranges: UCS <= 4.0.11, <= 5.4.6, <= 5.5.1, or <= 5.4.4Affected if The installed UCS version falls within any of the affected version ranges listed
-
Verify if UCS web management interface is enabledCheck the phone admin settings under Settings > Security > Web Server, or attempt to access http or https on the device IP addressAffected if HTTP or HTTPS web management is enabled and accessible
-
Determine network accessibility of the web interfaceCheck firewall rules, VLAN configuration, or access lists that control access to the phone management ports (80/443). Confirm whether the interface is exposed to untrusted networksAffected if The web interface is reachable from networks outside your trusted administrative zone
You are affected if you have Polycom SoundStation IP, VVX, or RealPresence Trio phones running UCS versions within the affected ranges with the web management interface enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade UCS firmware to version 4.0.12, 5.4.5 rev AG, 5.4.7, 5.5.2, 5.6.0 or later. Restrict web management interface access to trusted networks or disable HTTP/HTTPS management if not required.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12857 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12857 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data