dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2014-3362

HIGH · 7.8 CVSS v2.0 Published 2014-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
Memory leak in Cisco TelePresence System Edge MXP Series Software F9.3.3 and earlier allows remote attackers to cause a denial of service (management outage) via multiple TELNET connections, aka Bug ID CSCuo63677.

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

Memory leak vulnerability in Cisco TelePresence System Edge MXP Series Software F9.3.3 and earlier allows remote attackers to cause denial of service via multiple TELNET connections. Each TELNET connection consumes memory that is not properly released, eventually exhausting available memory and causing management interface outage.

MitigationUpgrade to fixed Cisco software version; if upgrade not immediately feasible, disable TELNET and use SSH for management access, and/or restrict network access to management interfaces via ACLs.

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:<= f9.3.3= f9.0.1= f9.0.2= f9.1.0= f9.1.1= f9.1.2= f9.3= f9.3.1= fnc9.1.0= fnc9.1.1= fnc9.1.2= fnc9.3
Telepresence System Edge 75 MxpHardware / appliance
Affected:all versions
Telepresence System Edge 85 MxpHardware / appliance
Affected:all versions
Telepresence System Edge 95 MxpHardware / 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
None
Integrity
None
Availability
Complete

AV:N/AC:L/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 management interface or use the command line to display system information. Look for model identifiers such as Edge 75 MXP, Edge 85 MXP, or Edge 95 MXP.
    Affected if The device is an Edge 75 MXP, Edge 85 MXP, or Edge 95 MXP model (all versions are affected).
  2. Determine the software version
    Execute the command to display the software version (commonly 'show version' or similar in the device CLI). Compare the installed version against the affected range: f9.3.3 and earlier, including f9.0.1, f9.0.2, f9.1.0, f9.1.1, f9.1.2, f9.3, f9.3.1, fnc9.1.0, fnc9.1.1, fnc9.1.2, fnc9.3.
    Affected if The software version is f9.3.3 or any earlier f9.x or fnc9.x version listed in the affected versions.
  3. Verify if TELNET management access is enabled
    Check the device configuration for TELNET service settings. Look for commands such as 'telnet enable' or check the management access settings in the device configuration files.
    Affected if TELNET is enabled for remote management access. The vulnerability requires TELNET to be active to be exploitable.
  4. Check for symptoms of memory exhaustion
    Monitor available system memory using device diagnostics (commonly 'show memory' or 'system diagnostics' commands). Look for consistently decreasing available memory or abnormally low free memory values.
    Affected if The device shows abnormally low or depleting memory resources, especially if multiple TELNET sessions have been opened.

A user is affected if they have a Cisco TelePresence Edge 75/85/95 MXP (any version) or software version f9.3.3/earlier, and TELNET management access is enabled, as the memory leak only occurs through TELNET connections.

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

Upgrade to fixed Cisco software version; if upgrade not immediately feasible, disable TELNET and use SSH for management access, and/or restrict network access to management interfaces via ACLs.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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