dbcve.org
Telepresence Mcu SoftwareApplication · Cisco

CVE-2017-3792

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 a proprietary device driver in the kernel of Cisco TelePresence Multipoint Control Unit (MCU) Software could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition. The vulnerability is due to improper size validation when reassembling fragmented IPv4 or IPv6 packets. An attacker could exploit this vulnerability by sending crafted IPv4 or IPv6 fragments to a port receiving content in Passthrough content mode. An exploit could allow the attacker to overflow a buffer. If successful, the attacker could execute arbitrary code or cause a DoS condition on the affected system. Cisco TelePresence MCU platforms TelePresence MCU 5300 Series, TelePresence MCU MSE 8510 and TelePresence MCU 4500 are affected when running software version 4.3(1.68) or later configured for Passthrough content mode. Cisco has released software updates that address this vulnerability. Workarounds that address this vulnerability are not available, but mitigations are available. Cisco Bug IDs: CSCuu67675.

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 buffer overflow vulnerability exists in the kernel device driver of Cisco TelePresence MCU software due to improper size validation during IPv4/IPv6 packet fragment reassembly. When configured in Passthrough content mode, the device fails to properly validate fragment sizes, allowing an attacker to overflow a buffer by sending crafted fragments to a targeted port.

MitigationApply the Cisco software updates that address this vulnerability. Since no workarounds are available, implement available mitigations and ensure affected MCU platforms (5300 Series, MSE 8510, 4500) running version 4.3(1.68) or later are patched.

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 Mcu SoftwareApplication
Affected:= 4.3_\(1.68\)= 4.3_\(2.18\)= 4.3_\(2.30\)= 4.3_\(2.32\)= 4.4_\(3.42\)= 4.4_\(3.49\)= 4.4_\(3.54\)= 4.4_\(3.57\)= 4.4_\(3.67\)= 4.5_\(1.45\)= 4.5_\(1.55\)= 4.5_\(1.71\)

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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 installed Cisco TelePresence MCU software version
    Access the MCU web interface or CLI and locate the software version information, typically found under System > Information or via the 'show version' command
    Affected if The version matches any of these: 4.3(1.68), 4.3(2.18), 4.3(2.30), 4.3(2.32), 4.4(3.42), 4.4(3.49), 4.4(3.54), 4.4(3.57), 4.4(3.67), 4.5(1.45), 4.5(1.55), or 4.5(1.71)
  2. Confirm the MCU model is a 5300 Series, MSE 8510, or 4500
    Check the hardware model via the web interface under System > Information or the 'show system' CLI command
    Affected if The device is a Cisco TelePresence MCU 5300 Series, MSE 8510, or 4500 platform
  3. Determine if Passthrough content mode is enabled
    Navigate to the MCU configuration settings, typically under Conference > Settings or Content > Passthrough, and check whether the Passthrough content mode is active
    Affected if Passthrough content mode is enabled and the version matches an affected release listed above

The device is affected if it is a Cisco TelePresence MCU 5300 Series, MSE 8510, or 4500 running any of the listed versions with Passthrough content mode configured.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco software updates that address this vulnerability. Since no workarounds are available, implement available mitigations and ensure affected MCU platforms (5300 Series, MSE 8510, 4500) running version 4.3(1.68) or later are patched.

Recommended fix Moderate confidence

Obtain fixed version from Cisco (contact TAC or check Cisco bug CSCuu67675) - the description indicates software updates are available but specific version numbers are not listed in the provided reference material

  1. Contact Cisco TAC or visit tools.cisco.com to obtain the specific fixed software version for CSCuu67675
  2. Upgrade Cisco TelePresence MCU Software to the fixed release provided by Cisco
  3. Verify the upgrade completes successfully
  4. If immediate upgrade is not possible, restrict network access to the MCU's Passthrough content mode port and implement firewall rules to limit exposure to untrusted IPv4/IPv6 sources
Caveat Review Cisco release notes for any compatibility considerations before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Telepresence Mcu Software 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 help mitigating

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-2017-3792 — 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-3792 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