dbcve.org
Tivoli MonitoringApplication · Ibm

CVE-2013-0551

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
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 (abend) via a crafted 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

The Basic Services component in IBM Tivoli Monitoring (ITM) versions 6.2.0 through 6.2.3 and IBM Application Manager for Smart Business 1.2.1 contains a vulnerability where specially crafted URLs can trigger an application crash (abend), resulting in denial of service. The attack is remote and requires no authentication.

MitigationApply IBM fix packs: FP3 or later for ITM 6.2.0-6.2.3, FP4 for 6.2.1, FP9 for 6.2.2; for IBM Application Manager apply 1.2.1.0-TIV-IAMSB-FP0004 or later. If immediate patching is not feasible, implement network-level filtering to block suspicious URL patterns.

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. Identify installed IBM Tivoli Monitoring version
    Run 'itmcmd version' or check the installation directory for version info files. On Windows, check Add/Remove Programs for IBM Tivoli Monitoring version. On Unix, check the installation path typically under /opt/IBM/ITM and look for version files.
    Affected if Version matches 6.2.0 through 6.2.3 (any of: 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)
  2. Identify installed IBM Application Manager for Smart Business version
    Check installation directory or Add/Remove Programs for IBM Application Manager for Smart Business version number.
    Affected if Version is exactly 1.2.1 or earlier 1.2.x versions
  3. Confirm Basic Services component is exposed
    Verify that the Basic Services web interface port is accessible. Default ITM ports include 1920, 3660, or 8080. Check if the CandleBasic web application is running by accessing the hostname on the configured port.
    Affected if Basic Services component (CandleBasic) is accessible via network and responding to HTTP requests
  4. Review application crash logs for URL-triggered abends
    Check ITM logs in the <ITM_HOME>/logs directory or Windows Event Viewer for application crashes occurring around web requests. Look for 'abend', 'crash', or exception patterns in logs.
    Affected if Logs show application crashes correlating to web requests to the Basic Services component

Your environment is affected if you have IBM Tivoli Monitoring 6.2.0-6.2.3 or IBM Application Manager for Smart Business 1.2.1 installed with the Basic Services component exposed to network access.

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 IBM fix packs: FP3 or later for ITM 6.2.0-6.2.3, FP4 for 6.2.1, FP9 for 6.2.2; for IBM Application Manager apply 1.2.1.0-TIV-IAMSB-FP0004 or later. If immediate patching is not feasible, implement network-level filtering to block suspicious URL patterns.

Fix this in Tivoli Monitoring Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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