CVE-2019-10689
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 · uneditedVVX products using UCS software version 5.9.2 and earlier with Better Together over Ethernet Connector (BToE) application version 3.9.1 and earlier provides insufficient authentication between the BToE application and the BToE component, resulting in leakage of 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 · moderate confidenceThe Polycom VVVX phones with UCS software 5.9.2 and earlier and BToE application 3.9.1 and earlier have insufficient authentication between the Better Together over Ethernet Connector application and its component, allowing an attacker on the same network to intercept sensitive information.
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<= 3.9.1<= 5.9.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 BToE Connector versionOn the Windows system where BToE Connector is installed, open Programs and Features or check the application properties. The version is typically displayed in the application UI under Help > About, or in the Windows installed programs list.Affected if The installed version of Polycom Better Together Over Ethernet Connector is 3.9.1 or earlier.
-
Identify UCS software versionAccess the Polycom phone web interface or admin menu. Navigate to Settings > System Information, or check the phone's status screen for the UCS firmware version.Affected if The installed UCS firmware version is 5.9.2 or earlier.
-
Determine if BToE functionality is enabledCheck the BToE Connector application settings on the Windows host, or verify via the phone's admin interface whether Better Together over Ethernet pairing is active. Look for BToE connection status in the system tray or application logs.Affected if BToE Connector is installed and the Better Together over Ethernet feature is actively paired or enabled between the phone and the Windows application.
-
Assess network segment exposureReview the network configuration to determine whether the device is connected to a trusted or untrusted network segment. Check VLAN assignment, network firewall rules, and whether the BToE ports are accessible from outside a trusted zone.Affected if The BToE communication occurs over a network segment that is not isolated or is accessible to untrusted users on the same network.
A user is affected if they have BToE Connector version 3.9.1 or earlier, or UCS version 5.9.2 or earlier, with BToE pairing enabled on a network segment that includes untrusted devices.
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 dataUpdate UCS software to a version newer than 5.9.2 and BToE application to a version newer than 3.9.1, and ensure BToE connections are only permitted on trusted network segments.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10689 — 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-2019-10689 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