Telepresence CeApplication · Cisco

CVE-2019-1878

HIGH · 8.8 CVSS v3.0 Published 2019-06-20
Fix available
A fix is available. Upgrade to 7.3.17 / 8.3.7 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 Cisco Discovery Protocol (CDP) implementation for the Cisco TelePresence Codec (TC) and Collaboration Endpoint (CE) Software could allow an unauthenticated, adjacent attacker to inject arbitrary shell commands that are executed by the device. The vulnerability is due to insufficient input validation of received CDP packets. An attacker could exploit this vulnerability by sending crafted CDP packets to an affected device. A successful exploit could allow the attacker to execute arbitrary shell commands or scripts on the targeted device.

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

This is a command injection vulnerability in Cisco Discovery Protocol (CDP) parsing on Cisco TelePresence TC and CE software. An unauthenticated, adjacent attacker (same Layer 2 network) can send specially crafted CDP packets with embedded shell commands that get executed by the device due to insufficient input validation. This allows full shell access without credentials.

MitigationApply the vendor patch/firmware update from Cisco for TelePresence TC and CE software. Until patched, segment affected devices on separate VLANs or disable CDP if not required to reduce attack surface from adjacent attackers.

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 CeApplication
Affected:>= 8.0.0, < 8.3.7>= 9.1.0, < 9.5.3>= 9.6.0, < 9.6.3
Telepresence TcApplication
Affected:>= 7.0.0, < 7.3.17

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

CVSS:3.0/AV:A/AC:L/PR:N/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 TelePresence software version
    Log into the device CLI and run 'show version' or 'sysversion' to obtain the installed software version. Note whether it is TC or CE branch.
    Affected if The version displayed matches any of the affected ranges: CE >= 8.0.0 and < 8.3.7, CE >= 9.1.0 and < 9.5.3, CE >= 9.6.0 and < 9.6.3, or TC >= 7.0.0 and < 7.3.17
  2. Confirm CDP protocol is enabled
    Run 'show cdp neighbors' or 'show cdp' to verify Cisco Discovery Protocol is operational on the device.
    Affected if CDP is active and the device is advertising and receiving CDP advertisements
  3. Verify Layer 2 network exposure
    Review the network configuration to determine if the device is on a shared or untrusted Layer 2 segment with untrusted endpoints. Check VLAN assignments and port security settings.
    Affected if The device is on a VLAN or switchport that allows adjacent unauthenticated attackers to reach it (same Layer 2 broadcast domain)

The device is affected if it runs a TelePresence TC or CE version within the affected ranges AND has CDP enabled AND is accessible to adjacent attackers on the same Layer 2 network.

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 7.3.17 / 8.3.7 / 9.5.3 or later
Fixed in 7.3.178.3.79.5.3
Interim mitigation

Apply the vendor patch/firmware update from Cisco for TelePresence TC and CE software. Until patched, segment affected devices on separate VLANs or disable CDP if not required to reduce attack surface from adjacent attackers.

Fix this in Telepresence Ce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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