Tivoli Netcool Application Service MonitorsApplication · Ibm

CVE-2013-0509

HIGH · 7.6 CVSS v2.0 Published 2013-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/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
Buffer overflow in the Transaction MIB agent in IBM Tivoli Netcool System Service Monitors (SSM) and Application Service Monitors (ASM) 4.0.0 before FP14 allows remote attackers to execute arbitrary code via a SQL transaction with a long table name that is not properly handled by a packet decoder.

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 vulnerability in the Transaction MIB agent of IBM Tivoli Netcool System Service Monitors (SSM) and Application Service Monitors (ASM) versions 4.0.0 through earlier than FP14. The vulnerability is triggered by processing SQL transactions containing overly long table names that are not properly validated by the packet decoder, allowing remote attackers to achieve arbitrary code execution.

MitigationUpgrade IBM Tivoli Netcool SSM/ASM to Fix Pack 14 (FP14) or later to patch the buffer overflow in the Transaction MIB agent's packet decoder.

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 Netcool Application Service MonitorsApplication
Affected:= 4.0.0
Tivoli Netcool System Service MonitorsApplication
Affected:= 4.0.0

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
High
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/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. Confirm IBM Tivoli Netcool ASM or SSM installation
    Look for the product installation directory, typically under /opt/IBM/tivoli/netcool or C:\Program Files\IBM\tivoli\netcool on Windows. Check for running processes named nco_pigeon, ncoasm, or ncossm.
    Affected if IBM Tivoli Netcool Application Service Monitors or System Service Monitors is installed and running
  2. Determine installed product version
    Check the version file in the installation directory, commonly named version.txt, or run the product's version command such as 'ncoasm -version' or 'ncossm -version' from the bin directory.
    Affected if The installed version is 4.0.0 through any version earlier than Fix Pack 14 (FP14)
  3. Check if Transaction MIB agent is enabled
    Look for the Transaction MIB agent process (typically nco_pigeon or similar MIB-related process) in the running processes, or check the product's configuration file (such as asm_config.xml or ssm_config.xml) for Transaction MIB agent settings.
    Affected if Transaction MIB agent is enabled and processing SQL transactions
  4. Verify SQL transaction handling is active
    Examine the product logs or configuration for SQL transaction processing capabilities. Check if the product is configured to receive or process SQL transactions from network sources.
    Affected if SQL transaction processing is enabled and the product accepts SQL input from network sources

The environment is affected if IBM Tivoli Netcool ASM or SSM version 4.0.0 through earlier than FP14 is installed with the Transaction MIB agent enabled and SQL transaction processing active.

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 IBM Tivoli Netcool SSM/ASM to Fix Pack 14 (FP14) or later to patch the buffer overflow in the Transaction MIB agent's packet decoder.

Fix this in Tivoli Netcool Application Service Monitors Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-0509 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