Telepresence Collaboration EndpointApplication · Cisco

CVE-2019-15277

MEDIUM · 6.7 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to 9.8.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability in the CLI of Cisco TelePresence Collaboration Endpoint (CE) Software could allow an authenticated, local attacker to execute code with root privileges. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by authenticating as the remote support user and sending malicious traffic to a listener who is internal to the device. A successful exploit could allow the attacker to execute commands with root privileges.

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 confidence

This is a local privilege escalation vulnerability in the CLI of Cisco TelePresence Collaboration Endpoint (CE) Software. An attacker who can authenticate as the 'remote support user' can send specially crafted malicious traffic to an internal listener, and due to insufficient input validation, achieve arbitrary code execution with root privileges.

MitigationImmediately change the default password for the remote support user account and disable the account if not required for legitimate support operations. Restrict physical and local network access to prevent unauthorized individuals from authenticating to the device.

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
Telepresence Collaboration EndpointApplication
Affected:< 9.8.0

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco TelePresence CE software is running
    Identify the device as a Cisco TelePresence Collaboration Endpoint system by reviewing system information via the administrative interface or CLI command that displays the software platform.
    Affected if The device is running Cisco TelePresence Collaboration Endpoint (CE) Software.
  2. Check installed software version
    Retrieve the current software version using the appropriate command or interface that displays the CE software version number.
    Affected if The installed version is lower than 9.8.0 (for example, 9.7.x, 9.6.x, etc.).
  3. Verify remote support user account status
    Check whether the 'remote support user' account exists and is enabled on the system through user account configuration settings or CLI commands that list local accounts.
    Affected if The 'remote support user' account is present and enabled on the device.
  4. Assess remote support user authentication capability
    Determine if the remote support user can authenticate to the device by verifying account credentials and access methods.
    Affected if The remote support user account can authenticate using its configured password.

A device is affected if it runs Cisco TelePresence CE software version below 9.8.0 and the remote support user account is enabled and accessible for authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 9.8.0 or later
Fixed in 9.8.0
Interim mitigation

Immediately change the default password for the remote support user account and disable the account if not required for legitimate support operations. Restrict physical and local network access to prevent unauthorized individuals from authenticating to the device.

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15277 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15277 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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