dbcve.org
Telepresence Mcu 4500 Series SoftwareApplication · Cisco

CVE-2013-1176

HIGH · 7.1 CVSS v2.0 Published 2013-04-18
Fix available
A fix is available. Upgrade to after 4.3 or later.
See remediation →
80/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
The DSP card on Cisco TelePresence MCU 4500 and 4501 devices before 4.3(2.30), TelePresence MCU MSE 8510 devices before 4.3(2.30), and TelePresence Server before 2.3(1.55) does not properly validate H.264 data, which allows remote attackers to cause a denial of service (device reload) via crafted RTP packets in a (1) SIP session or (2) H.323 session, aka Bug IDs CSCuc11328 and CSCub05448.

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

The DSP (Digital Signal Processor) card in Cisco TelePresence MCU 4500/4501 and MSE 8510 devices, as well as TelePresence Server, fails to properly validate H.264 video stream data. Attackers can send specially crafted RTP packets containing malformed H.264 payloads through SIP or H.323 signaling sessions, causing the device to reload and experience denial of service.

MitigationApply vendor-supplied firmware updates: upgrade TelePresence MCU 4500/4501 and MSE 8510 to version 4.3(2.30) or later, and TelePresence Server to version 2.3(1.55) or later. Consider network segmentation to limit exposure of these devices to untrusted networks.

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 4500 Series SoftwareApplication
Affected:<= 4.3\(2.18\)= 4.1\(1.51\)= 4.1\(1.59\)= 4.2\(1.43\)= 4.2\(1.46\)= 4.2\(1.50\)= 4.3\(1.68\)
Telepresence Mcu 4505Hardware / appliance
Affected:all versions
Telepresence Mcu 4510Hardware / appliance
Affected:all versions
Telepresence Mcu 4515Hardware / appliance
Affected:all versions
Telepresence Mcu 4520Hardware / appliance
Affected:all versions
Telepresence Mcu 4501 Series SoftwareApplication
Affected:<= 4.3\(2.18\)= 4.1\(1.51\)= 4.1\(1.59\)= 4.2\(1.43\)= 4.2\(1.46\)= 4.2\(1.50\)= 4.3\(1.68\)
Telepresence Mcu 4501Hardware / appliance
Affected:all versions
Telepresence Mcu Mse Series SoftwareApplication
Affected:<= 4.3\(2.18\)= 4.1\(1.51\)= 4.1\(1.59\)= 4.2\(1.43\)= 4.2\(1.46\)= 4.2\(1.50\)= 4.3\(1.68\)

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:N/C:N/I:N/A:C

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 device model
    Access the device admin interface or use CLI command 'show version' to confirm the exact model (MCU 4500, 4501, 4505, 4510, 4515, 4520, MSE 8510, or TelePresence Server)
    Affected if model is any of the listed affected products
  2. Check the installed software version
    Run 'show version' in CLI or check admin interface; compare against affected versions: 4.1(1.51), 4.1(1.59), 4.2(1.43), 4.2(1.46), 4.2(1.50), 4.3(1.68), or any version <= 4.3(2.18) for 4500/4501/MSE; for 4505/4510/4515/4520 all versions are affected
    Affected if version matches any of the listed vulnerable versions or falls within the <= 4.3(2.18) range for 4500/4501/MSE series, or is any version for 4505/4510/4515/4520
  3. Verify if SIP or H.323 signaling is enabled
    Check device configuration via CLI 'show running-config' or admin interface for sip or h323 protocol settings under the conferencing or gateway configuration
    Affected if SIP or H.323 signaling is enabled and the device accepts external calls
  4. Confirm H.264 video capability is active
    Review conference profiles or codec settings to determine if H.264 encoding/decoding is configured for any active conferences or presets
    Affected if H.264 video profiles are configured and actively used

The environment is affected if the device is a vulnerable model, runs an affected software version, and has SIP or H.323 signaling enabled with H.264 capability in use.

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 a release after 4.3
Interim mitigation

Apply vendor-supplied firmware updates: upgrade TelePresence MCU 4500/4501 and MSE 8510 to version 4.3(2.30) or later, and TelePresence Server to version 2.3(1.55) or later. Consider network segmentation to limit exposure of these devices to untrusted networks.

Fix this in Telepresence Mcu 4500 Series Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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