dbcve.org
Telepresence Advanced Media GatewayApplication · Cisco

CVE-2015-0713

HIGH · 9.0 CVSS v2.0 Published 2015-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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 web framework in Cisco TelePresence Advanced Media Gateway Series Software before 1.1(1.40), Cisco TelePresence IP Gateway Series Software, Cisco TelePresence IP VCR Series Software before 3.0(1.27), Cisco TelePresence ISDN Gateway Software before 2.2(1.94), Cisco TelePresence MCU Software before 4.4(3.54) and 4.5 before 4.5(1.45), Cisco TelePresence MSE Supervisor Software before 2.3(1.38), Cisco TelePresence Serial Gateway Series Software before 1.0(1.42), Cisco TelePresence Server Software for Hardware before 3.1(1.98), and Cisco TelePresence Server Software for Virtual Machine before 4.1(1.79) allows remote authenticated users to execute arbitrary commands with root privileges via unspecified vectors, aka Bug IDs CSCul55968, CSCur08993, CSCur15803, CSCur15807, CSCur15825, CSCur15832, CSCur15842, CSCur15850, and CSCur15855.

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

Command injection vulnerability in the web framework of multiple Cisco TelePresence product lines allows remote authenticated users to execute arbitrary OS commands with root privileges through unspecified vectors in the web interface.

MitigationApply the vendor-supplied patches: upgrade to Cisco TelePresence Advanced Media Gateway Software 1.1(1.40), IP VCR Software 3.0(1.27), ISDN Gateway Software 2.2(1.94), MCU Software 4.4(3.54) or 4.5(1.45), MSE Supervisor Software 2.3(1.38), Serial Gateway Software 1.0(1.42), Server Hardware Software 3.1(1.98), or Server VM Software 4.1(1.79) or later. Until patched, restrict web management interface access to trusted networks only.

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 Advanced Media GatewayApplication
Affected:= 1.0\(.1.13\)= 1.1\(.1.14\)= 1.1\(1.34\)
Telepresence Ip GatewayApplication
Affected:= 2.0.1.7= 2.0.1.11= 2.0.3.34
Telepresence Ip Vcr 1.0 ConverterApplication
Affected:= 1.0\(1.9\)
Telepresence Ip Vcr 2.4Application
Affected:= 1.2
Telepresence Ip Vcr 3.0Application
Affected:= 1.22= 1.24
Telepresence Isdn Gw 3241Application
Affected:= 2.0\(1.51\)= 2.1\(1.22\)= 2.1\(1.43\)= 2.1\(1.49\)= 2.1\(1.56\)
Telepresence Mcu SoftwareApplication
Affected:= 4.1\(1.51\)= 4.1\(1.59\)= 4.2\(1.43\)= 4.2\(1.46\)= 4.2\(1.50\)= 4.3\(1.68\)= 4.3\(2.18\)= 4.3\(2.30\)= 4.3\(2.32\)= 4.4\(3.42\)= 4.4\(3.49\)
Telepresence Serial GatewayApplication
Affected:= 1.0.1.23= 1.0.1.34= 1.0.1.38

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

AV:N/AC:L/Au:S/C:C/I:C/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 product model
    Access the device admin interface or CLI and retrieve the exact product name (e.g., Cisco Telepresence Advanced Media Gateway, Cisco Telepresence Ip Gateway, Cisco Telepresence Mcu Software, etc.)
    Affected if The product matches one of the affected product lines listed in the CVE
  2. Retrieve the installed software version
    Use the device CLI or web admin interface to view the current software version (typically found in system info, about, or version settings)
    Affected if The installed version matches any of the specific version numbers listed for that product in the CVE (e.g., for MCU Software: 4.1(1.51), 4.1(1.59), 4.2(1.43), etc.)
  3. Confirm web management interface is enabled
    Check device network settings or security configuration to verify the web-based management interface is active and accessible
    Affected if The web interface is enabled and reachable over the network (the vulnerability is exploited through this vector)
  4. Verify web interface authentication status
    Review user accounts and authentication settings for the web management portal to determine if remote authentication is possible
    Affected if Remote authentication to the web interface is permitted (the CVE requires authenticated user access)

The environment is affected if the device runs one of the listed TelePresence product lines with a version matching the CVE version list AND has the web management interface accessible with remote authentication 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.

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

Apply the vendor-supplied patches: upgrade to Cisco TelePresence Advanced Media Gateway Software 1.1(1.40), IP VCR Software 3.0(1.27), ISDN Gateway Software 2.2(1.94), MCU Software 4.4(3.54) or 4.5(1.45), MSE Supervisor Software 2.3(1.38), Serial Gateway Software 1.0(1.42), Server Hardware Software 3.1(1.98), or Server VM Software 4.1(1.79) or later. Until patched, restrict web management interface access to trusted networks only.

Recommended fix High confidence

Upgrade to the minimum fixed version for your specific product (e.g., Advanced Media Gateway 1.1(1.40), IP VCR 3.0(1.27), MCU Software 4.4(3.54) or later)

  1. 1. Identify the specific Cisco TelePresence product model running in your environment from the affected product list
  2. 2. Determine the current software version by accessing the device management interface or using 'show version' command
  3. 3. Based on the product type, identify the minimum fixed version required: Advanced Media Gateway >= 1.1(1.40), IP Gateway > 2.0.3.34, IP VCR >= 3.0(1.27), ISDN Gateway >= 2.2(1.94), MCU Software >= 4.4(3.54) or 4.5(1.45), Serial Gateway >= 1.0(1.42), MSE Supervisor >= 2.3(1.38), Server Hardware >= 3.1(1.98), Server Virtual Machine >= 4.1(1.79)
  4. 4. Obtain the appropriate software upgrade from Cisco (requires valid service contract)
  5. 5. Review Cisco release notes for any migration requirements or prerequisites
  6. 6. Back up current device configuration
  7. 7. Upload and install the new software version following Cisco upgrade procedures
  8. 8. Verify the new version is installed and the device is functioning normally
Caveat Upgrading between major versions may require configuration migration; ensure compatibility with any integrated systems and review Cisco migration guides

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

Fix this in Telepresence Advanced Media Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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