dbcve.org
Telepresence System Tx9000Hardware / appliance · Cisco

CVE-2013-3454

HIGH · 10.0 CVSS v2.0 Published 2013-08-08
Fix available
A fix is available. Upgrade to after 1.10.1 or later.
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
Cisco TelePresence System Software 1.10.1 and earlier on 500, 13X0, 1X00, 30X0, and 3X00 devices, and 6.0.3 and earlier on TX 9X00 devices, has a default password for the pwrecovery account, which makes it easier for remote attackers to modify the configuration or perform arbitrary actions via HTTPS requests, aka Bug ID CSCui43128.

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 Cisco TelePresence System Software contains a default password for the 'pwrecovery' administrative account, allowing remote unauthenticated attackers to authenticate via HTTPS and modify system configuration or execute arbitrary actions. This affects multiple device series (500, 13X0, 1X00, 30X0, 3X00, TX 9X00) across specific version ranges.

MitigationImmediately change or disable the default pwrecovery account password on all affected Cisco TelePresence devices, and restrict HTTPS management access to trusted IP addresses or networks to prevent external exploitation.

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 System Tx9000Hardware / appliance
Affected:all versions
Telepresence System Tx9200Hardware / appliance
Affected:all versions
Telepresence System SoftwareApplication
Affected:= 1.9.0\(46\)= 1.9.0.1\(3\)= 1.9.1\(68\)= 1.9.2= 1.9.3= 1.9.4= 1.9.5= 1.9.6= 6.0.0.1\(4\)= 6.0.1\(50\)= 6.0.2\(28\)<= 1.10.1
Telepresence System 1300Hardware / appliance
Affected:all versions
Telepresence System 1300 65Hardware / appliance
Affected:all versions
Telepresence System 3000Hardware / appliance
Affected:all versions
Telepresence System 3010Hardware / appliance
Affected:all versions
Telepresence System 3200Hardware / appliance
Affected:all versions

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

AV:N/AC:L/Au:N/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 device model
    Log into the Cisco TelePresence device admin interface or use CLI command 'show system/unit info' to determine the exact model number. Check if it matches any of the affected series: 500, 13X0, 1X00, 30X0, 3X00, TX 9000, TX 9200, 1300, 1300 65, 3000, 3010, or 3200.
    Affected if Device model is one of the listed affected series.
  2. Check software version
    Access the device CLI or admin interface and run 'show version' or navigate to the software version information page. Compare the installed version against the affected version list: 1.9.0(46), 1.9.0.1(3), 1.9.1(68), 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 6.0.0.1(4), 6.0.1(50), 6.0.2(28), any version 1.10.1 or lower, or all versions of Tx9000/Tx9200.
    Affected if Installed software version matches any version in the affected list or is an 'all versions' model.
  3. Verify HTTPS management access
    Attempt to access the device HTTPS management interface from a remote host by browsing to https://<device-ip>/ or using an HTTP client to probe port 443. Confirm the interface responds and is reachable from untrusted networks.
    Affected if HTTPS management interface is accessible from networks where untrusted users could connect.
  4. Confirm pwrecovery account status
    Log into the device admin interface and navigate to User Management or Accounts settings. Look for an account named 'pwrecovery' and verify whether it exists and is enabled. The account should not be present or should be disabled on a properly configured system.
    Affected if The 'pwrecovery' account exists and is enabled on the device.

The environment is affected if the device is a Cisco TelePresence model from the affected series, runs an affected software version, has HTTPS management exposed, and retains the default pwrecovery account 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
Upgrade available Upgrade to a release after 1.10.1
Interim mitigation

Immediately change or disable the default pwrecovery account password on all affected Cisco TelePresence devices, and restrict HTTPS management access to trusted IP addresses or networks to prevent external exploitation.

Recommended fix Moderate confidence

Cisco TelePresence System Software version > 1.10.1 (or > 6.0.3 for TX 9X00 series); contact Cisco for exact fixed release for your specific model

  1. 1. Identify the exact Cisco TelePresence System model and current software version by accessing the administrative web interface or using the 'show version' command via CLI.
  2. 2. Based on the official description, upgrade to a version higher than 1.10.1 for 500, 13X0, 1X00, 30X0, and 3X00 devices, or higher than 6.0.3 for TX 9X00 devices.
  3. 3. Download the appropriate updated Cisco TelePresence System Software from the Cisco Software Download Center (software.cisco.com) after authenticating with valid service contract.
  4. 4. Back up the current system configuration using the administrative interface or 'export configuration' command.
  5. 5. Upload and install the new software version following Cisco's standard upgrade procedure (typically via the administration GUI under 'Software Upgrade' or 'System > Software' path).
  6. 6. After upgrade, immediately change any default passwords for all accounts, especially the pwrecovery account if it still exists, using the 'admin' or 'system' settings.
  7. 7. Verify the upgrade was successful by checking the new software version and testing basic call functionality.
  8. 8. Ensure the device is not directly accessible from the internet by placing it behind a properly configured firewall.
Caveat Review Cisco release notes for your specific model for any breaking changes or migration requirements before upgrading; some legacy hardware may have limited upgrade paths

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

Fix this in Telepresence System Tx9000 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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