dbcve.org
Tivoli MonitoringApplication · Ibm

CVE-2013-2960

MEDIUM · 5.0 CVSS v2.0 Published 2013-06-21
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
Buffer overflow in KDSMAIN in the Basic Services component in IBM Tivoli Monitoring (ITM) 6.2.0 through FP3, 6.2.1 through FP4, 6.2.2 through FP9, and 6.2.3 before FP3, as used in IBM Application Manager for Smart Business (formerly Tivoli Foundations Application Manager) 1.2.1 before 1.2.1.0-TIV-IAMSB-FP0004 and other products, allows remote attackers to cause a denial of service (segmentation fault) via a crafted http URL.

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

Buffer overflow vulnerability in KDSMAIN component of IBM Tivoli Monitoring allows remote attackers to cause denial of service via crafted HTTP URLs. The vulnerability affects multiple fix pack levels across ITM versions 6.2.0 through 6.2.3 and IBM Application Manager for Smart Business 1.2.1.

MitigationApply the appropriate IBM fix packs: ITM 6.2.0 FP3, 6.2.1 FP4, 6.2.2 FP9, or 6.2.3 FP3 and later; IAMSB 1.2.1.0-TIV-IAMSB-FP0004 or later. Implement input validation at network perimeter for HTTP traffic to ITM services.

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
Tivoli MonitoringApplication
Affected:= 6.2.0= 6.2.0.1= 6.2.0.2= 6.2.0.3= 6.2.1= 6.2.1.1= 6.2.1.2= 6.2.1.3= 6.2.1.4= 6.2.2= 6.2.2.1= 6.2.2.2
Application Manager For Smart BusinessApplication
Affected:= 1.2.1

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. Confirm IBM Tivoli Monitoring or IBM Application Manager for Smart Business is installed
    Locate the ITM installation directory (commonly C:\IBM\ITM or /opt/IBM/ITM) and check for the presence of Tivoli Monitoring or IAMSB binaries and executables.
    Affected if The product is not installed - then not affected. If installed, proceed to version check.
  2. Identify the installed ITM or IAMSB version
    Run the 'tacmd listSystems' command or check the installation logs for the exact version number. On Windows, right-click 'KDSMAIN' in Task Manager and view Properties to see version info, or check the version from the installation directory properties.
    Affected if The installed version matches one of these: 6.2.0, 6.2.0.1, 6.2.0.2, 6.2.0.3, 6.2.1, 6.2.1.1, 6.2.1.2, 6.2.1.3, 6.2.1.4, 6.2.2, 6.2.2.1, 6.2.2.2, or 1.2.1 for IAMSB.
  3. Verify the KDSMAIN component is running
    Check if the KDSMAIN process is active. On Windows, open Task Manager and look for 'kdsmain.exe'. On Unix/Linux, run 'ps -ef | grep kdsmain' to list the running process.
    Affected if KDSMAIN is not running - then not vulnerable since the attack requires this component to be active.
  4. Confirm HTTP interface is enabled for KDSMAIN
    Check the KDSMAIN configuration file (typically kdsmain.ini or itm.ini in the installation directory) for HTTP listening settings. Use netstat or equivalent to check if port 1920 (default HTTP port for ITM) or configured HTTP port is listening.
    Affected if HTTP interface is enabled and port is listening, making the vulnerability exploitable via crafted HTTP URLs.

A user is affected if they have an affected ITM version (6.2.0 through 6.2.2.2) or IAMSB version (1.2.1) AND the KDSMAIN component is running with its HTTP interface exposed to network traffic.

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 appropriate IBM fix packs: ITM 6.2.0 FP3, 6.2.1 FP4, 6.2.2 FP9, or 6.2.3 FP3 and later; IAMSB 1.2.1.0-TIV-IAMSB-FP0004 or later. Implement input validation at network perimeter for HTTP traffic to ITM services.

Fix this in Tivoli Monitoring Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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