dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2011-0376

HIGH · 10.0 CVSS v2.0 Published 2011-02-25
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
The TFTP implementation on Cisco TelePresence endpoint devices with software 1.2.x through 1.5.x, 1.6.0, and 1.6.1 allows remote attackers to obtain sensitive information via a GET request, aka Bug ID CSCte43876.

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 TFTP server implementation on Cisco TelePresence endpoint devices (software versions 1.2.x through 1.5.x, 1.6.0, and 1.6.1) allows unauthenticated remote attackers to retrieve sensitive files via specially crafted GET requests. This information disclosure vulnerability has a critical CVSS score of 10 due to the trivial exploitability nature of TFTP protocol combined with network accessibility.

MitigationApply the Cisco patch for Bug ID CSCte43876 by upgrading to a supported software version. Until patched, restrict network access to UDP port 69 (TFTP) and disable TFTP services if not operationally required.

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 SoftwareApplication
Affected:= 1.2.3= 1.3.2= 1.4.7= 1.5.1= 1.5.3= 1.5.10= 1.5.11= 1.5.12= 1.5.13= 1.6.0= 1.6.1
Telepresence System 1000Hardware / appliance
Affected:all versions
Telepresence System 1100Hardware / appliance
Affected:all versions
Telepresence System 3000Hardware / appliance
Affected:all versions
Telepresence System 1300 SeriesHardware / appliance
Affected:all versions
Telepresence System 3200 SeriesHardware / appliance
Affected:all versions
Telepresence System 500 SeriesHardware / 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 the TelePresence device model
    Access the device admin interface or check the physical hardware label to determine if the device is a TelePresence System 1000, 1100, 3000, 1300 Series, 3200 Series, or 500 Series
    Affected if Device model is any of these series (all versions are affected)
  2. Check the software version
    Log into the device CLI or web interface and run 'show version' or navigate to the system information page to retrieve the installed software version
    Affected if Version equals 1.2.3, 1.3.2, 1.4.7, 1.5.1, 1.5.3, 1.5.10, 1.5.11, 1.5.12, 1.5.13, 1.6.0, or 1.6.1
  3. Verify TFTP service status
    Check the device configuration for TFTP server settings via CLI 'show running-config | include tftp' or via the admin web interface under services or network settings
    Affected if TFTP server is enabled on the device (vulnerability requires TFTP to be running)
  4. Test UDP port 69 accessibility
    From an external host, attempt to reach the device on UDP port 69 using 'nc -uv <device_ip> 69' or a TFTP client connection test
    Affected if UDP port 69 is open and reachable from untrusted networks

Device is affected if it is a Cisco TelePresence System 1000/1100/3000/1300/3200/500 (any version) or runs software version 1.2.3 through 1.6.1, and the TFTP service is enabled and accessible on UDP port 69.

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 the Cisco patch for Bug ID CSCte43876 by upgrading to a supported software version. Until patched, restrict network access to UDP port 69 (TFTP) and disable TFTP services if not operationally required.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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