Telepresence Collaboration EndpointApplication · Cisco

CVE-2019-15275

MEDIUM · 6.7 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to 9.8.1 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 arbitrary commands 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 submitting malicious input to a specific command. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system (OS) 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 · high confidence

A local privilege escalation vulnerability exists in the Cisco TelePresence Collaboration Endpoint (CE) Software CLI. An attacker with valid credentials for the 'remote support' user account can inject arbitrary OS commands through insufficient input validation in a specific CLI command, achieving root-level execution on the underlying operating system.

MitigationApply the vendor patch for CVE-2019-15275 (contact Cisco for affected versions), change the remote support user credentials immediately, and review access controls for CLI authentication.

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.1

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. Identify the product and version
    Access the Cisco TelePresence device CLI or web interface and retrieve the software version information using the command 'show version' or checking the system information page.
    Affected if The software version is Cisco TelePresence Collaboration Endpoint (CE) and the version is below 9.8.1.
  2. Verify the remote support user account exists
    Log into the device CLI with administrative credentials and check for the presence of the 'remote support' user account using 'show user' or by reviewing local user accounts.
    Affected if The 'remote support' user account is present and enabled on the system.
  3. Confirm CLI authentication is configured
    Check the device configuration for CLI authentication settings using 'show running-config | include authentication' or reviewing the security settings in the web interface.
    Affected if CLI authentication is enabled and the remote support user has valid login credentials.
  4. Review CLI command execution logs
    Examine system logs for any executed CLI commands, particularly those that may indicate command injection attempts or unusual activity from the remote support user account.
    Affected if There are logs of suspicious or unauthorized CLI command execution, especially involving shell commands.

Your environment is affected if you are running Cisco TelePresence Collaboration Endpoint (CE) software version below 9.8.1 with the remote support user account present and CLI access enabled.

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.1 or later
Fixed in 9.8.1
Interim mitigation

Apply the vendor patch for CVE-2019-15275 (contact Cisco for affected versions), change the remote support user credentials immediately, and review access controls for CLI authentication.

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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