dbcve.org
Ciscoworks Internetwork Performance MonitorApplication · Cisco

CVE-2010-0138

HIGH · 10.0 CVSS v2.0 Published 2010-01-21
Fix available
A fix is available. Upgrade to after 2.6 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
Buffer overflow in Cisco CiscoWorks Internetwork Performance Monitor (IPM) 2.6 and earlier on Windows, as distributed in CiscoWorks LAN Management Solution (LMS), allows remote attackers to execute arbitrary code via a malformed getProcessName CORBA General Inter-ORB Protocol (GIOP) request, related to a "third-party component," aka Bug ID CSCsv62350.

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

Buffer overflow in CiscoWorks Internetwork Performance Monitor (IPM) 2.6 and earlier on Windows (distributed in CiscoWorks LMS) allows remote attackers to execute arbitrary code via malformed getProcessName CORBA GIOP requests. The vulnerability is in a third-party component.

MitigationApply Cisco patch for Bug ID CSCsv62350 if available; otherwise, restrict network access to the IPM service or disable it until patching is possible.

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
Ciscoworks Internetwork Performance MonitorApplication
Affected:<= 2.6= 2.4= 2.5

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 if IPM is installed
    Check Windows services or installed programs for 'CiscoWorks Internetwork Performance Monitor' or 'IPM' service. Also check for CiscoWorks LMS installation directories (typically C:\Program Files\Cisco Systems\).
    Affected if The CiscoWorks IPM component or CiscoWorks LMS is installed on the system.
  2. Verify the IPM version
    Locate the IPM installation directory and check version information in file properties or check registry keys under HKLM\SOFTWARE\Cisco Systems for IPM version.
    Affected if The installed version is 2.6 or earlier (including 2.4 and 2.5).
  3. Confirm Windows platform
    Verify the operating system is Windows. This vulnerability only affects the Windows version of CiscoWorks IPM.
    Affected if The system is running Windows with IPM installed.
  4. Check if IPM service is running
    Open Windows Services console (services.msc) and check if the 'CiscoWorks IPM' or similar service is present and running. Also check for listening ports associated with CORBA GIOP (typically port 19191 or 19192).
    Affected if The IPM service is enabled and running, exposing the vulnerable CORBA GIOP interface.

A system is affected if CiscoWorks IPM version 2.6 or earlier (2.4, 2.5, or 2.6) is installed and running on Windows with the IPM/CORBA GIOP service 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 2.6
Interim mitigation

Apply Cisco patch for Bug ID CSCsv62350 if available; otherwise, restrict network access to the IPM service or disable it until patching is possible.

Recommended fix Moderate confidence

CiscoWorks IPM 2.6.1 or later (or CiscoWorks LMS with integrated fixed IPM version)

  1. Locate and access the Cisco Software Download center for CiscoWorks LMS and IPM
  2. Navigate to the downloads for CiscoWorks LAN Management Solution (LMS)
  3. Locate and download CiscoWorks IPM version 2.6.1 or later
  4. Apply the upgrade following standard CiscoWorks upgrade procedures
  5. Verify the version post-upgrade by checking the IPM component version
Caveat Test the upgrade in a non-production environment first as CiscoWorks upgrades may affect other integrated components

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

Fix this in Ciscoworks Internetwork Performance Monitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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