dbcve.org
Telepresence CeApplication · Cisco

CVE-2017-3825

HIGH · 7.5 CVSS v3.0 Published 2017-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 ICMP ingress packet processing of Cisco TelePresence Collaboration Endpoint (CE) Software could allow an unauthenticated, remote attacker to cause the TelePresence endpoint to reload unexpectedly, resulting in a denial of service (DoS) condition. The vulnerability is due to incomplete input validation for the size of a received ICMP packet. An attacker could exploit this vulnerability by sending a crafted ICMP packet to the local IP address of the targeted endpoint. A successful exploit could allow the attacker to cause a DoS of the TelePresence endpoint, during which time calls could be dropped. This vulnerability would affect either IPv4 or IPv6 ICMP traffic. This vulnerability affects the following Cisco TelePresence products when running software release CE8.1.1, CE8.2.0, CE8.2.1, CE8.2.2, CE 8.3.0, or CE8.3.1: Spark Room OS, TelePresence DX Series, TelePresence MX Series, TelePresence SX Quick Set Series, TelePresence SX Series. Cisco Bug IDs: CSCvb95396.

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

A vulnerability in the ICMP ingress packet processing of Cisco TelePresence CE software allows unauthenticated remote attackers to cause unexpected device reloads by sending crafted ICMP packets with improper size validation, resulting in denial of service.

MitigationApply Cisco's patched software version to address the incomplete input validation vulnerability in ICMP packet processing.

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.1.0= 8.2.0
Telepresence TcApplication
Affected:= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 5.1.11= 5.1.13= 6.0.2= 6.0.3= 6.0.4= 6.1.3= 6.1.4

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Access the device command line interface and run 'show version' or check the system information page in the web interface to obtain the exact software version number
    Affected if The displayed version matches any of these: CE 8.0.0, 8.1.0, 8.2.0, or TC 4.2.0 through 4.2.4, 5.1.11, 5.1.13, 6.0.2, 6.0.3, 6.0.4, 6.1.3, or 6.1.4
  2. Confirm the software variant is CE or TC
    Verify the device is running Cisco TelePresence CE or TelePresence TC software by checking the product description in 'show version' output
    Affected if The software variant shows 'CE' or 'TC' in the product name or version string
  3. Verify ICMP processing is enabled
    Check the device network configuration for ICMP processing settings - typically found via 'show running-config' or the network settings in the web interface, looking for ICMP or 'ping' related settings
    Affected if ICMP/ping response is permitted (this is the default state on most installations)
  4. Check network exposure of the device
    Review firewall rules and network access controls to determine if the TelePresence device is reachable from untrusted networks on its management or signaling interfaces
    Affected if The device management or primary interface is accessible from networks you do not control or from the internet

You are affected if the device runs TelePresence CE version 8.0.0-8.2.0 or TC version 4.2.0-6.1.4 and has ICMP processing enabled and network accessibility from potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's patched software version to address the incomplete input validation vulnerability in ICMP packet processing.

Fix this in Telepresence Ce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-3825 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