dbcve.org
Prime Lan Management SolutionApplication · Cisco

CVE-2013-5488

MEDIUM · 5.0 CVSS v2.0 Published 2013-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 →
59/100
Remediation priority · Elevated
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 Common Services, as used in Cisco Prime LAN Management Solution (LMS), Cisco Security Manager, Cisco Unified Service Monitor, and Cisco Unified Operations Manager, does not properly interact with the ActiveMQ component, which allows remote attackers to cause a denial of service (memory consumption) via simultaneous TCP sessions, aka Bug IDs CSCuh54766, CSCuh01267, CSCuh95976, and CSCuh95969.

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 · moderate confidence

Cisco Common Services in multiple Cisco management products (Prime LMS, Security Manager, Unified Service Monitor, Unified Operations Manager) improperly interacts with the ActiveMQ messaging component. Remote attackers can trigger memory exhaustion by establishing simultaneous TCP sessions to the ActiveMQ service, causing denial of service.

MitigationApply relevant Cisco patches associated with bug IDs CSCuh54766, CSCuh01267, CSCuh95976, and CSCuh95969. Consider implementing connection rate limiting on affected systems and network segmentation to limit exposure to the ActiveMQ ports.

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
Prime Lan Management SolutionApplication
Affected:all versions
Security ManagerApplication
Affected:all versions
Unified Operations ManagerApplication
Affected:all versions
Unified Service MonitorApplication
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
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 installed Cisco management products
    Review installed software on the system for any of these: Cisco Prime LMS, Cisco Security Manager, Cisco Unified Operations Manager, or Cisco Unified Service Monitor. Check Windows Services or Linux init scripts for processes containing 'Cisco' and 'Manager' in the name.
    Affected if Any of the four affected products (Prime LMS, Security Manager, Unified Operations Manager, Unified Service Monitor) are installed - all versions are vulnerable
  2. Locate the ActiveMQ service
    On the system running the Cisco product, search for ActiveMQ processes. On Windows, check services named 'ActiveMQ' or look for 'activemq' in running processes. On Linux, run 'ps -ef | grep -i activemq' or check /opt for activemq directories.
    Affected if ActiveMQ is running as a service on the system hosting any of the affected Cisco products
  3. Identify ActiveMQ listening ports
    Run 'netstat -an' or 'ss -tlnp' and look for ports commonly used by ActiveMQ: 61616 (OpenWire), 61613 (STOMP), 8161 (web console), 5672 (AMQP). Also check for any non-standard ports configured for ActiveMQ in the product documentation.
    Affected if ActiveMQ ports (61616, 61613, 8161, 5672) or product-specific ActiveMQ ports are listening and accessible over the network
  4. Detect high TCP connection count to ActiveMQ
    Use 'netstat -an | grep <ActiveMQ_port>' or 'ss -tn state established' repeatedly to count current TCP connections to ActiveMQ ports. Compare against baseline normal connections. Watch for rapid accumulation of simultaneous connections.
    Affected if An unusually high number of concurrent TCP connections to ActiveMQ ports is observed, especially from external IP addresses
  5. Monitor system memory for exhaustion
    Monitor available physical memory on the server (task manager on Windows, 'free -m' or 'top' on Linux). Observe if memory usage spikes or remains abnormally high while ActiveMQ is running.
    Affected if System exhibits high memory usage or memory exhaustion symptoms that correlate with ActiveMQ being accessible over the network

A user is affected if any of the four Cisco products (Prime LMS, Security Manager, Unified Operations Manager, Unified Service Monitor) is installed with ActiveMQ exposed on the network and experiencing high concurrent TCP connection counts.

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 relevant Cisco patches associated with bug IDs CSCuh54766, CSCuh01267, CSCuh95976, and CSCuh95969. Consider implementing connection rate limiting on affected systems and network segmentation to limit exposure to the ActiveMQ ports.

Fix this in Prime Lan Management Solution Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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