dbcve.org
Db2Application · Ibm

CVE-2012-1796

HIGH · 7.2 CVSS v2.0 Published 2012-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Unspecified vulnerability in IBM Tivoli Monitoring Agent (ITMA), as used in IBM DB2 9.5 before FP9 on UNIX, allows local users to gain privileges via unknown vectors.

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

Local privilege escalation vulnerability in IBM Tivoli Monitoring Agent (ITMA) as used in IBM DB2 9.5 before FP9 on UNIX systems. Allows local users to gain elevated privileges through unspecified vectors.

MitigationUpgrade IBM DB2 9.5 to Fix Pack 9 or later which contains the patched IBM Tivoli Monitoring Agent.

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
Db2Application
Affected:= 9.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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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. Confirm IBM DB2 9.5 is installed
    Run 'db2level' or 'db2pd -version' from a DB2 instance owner account to retrieve the installed DB2 version and build level
    Affected if The output shows DB2 version 9.5 is installed
  2. Determine the Fix Pack level
    Examine the version output for the Fix Pack number. The version string typically shows FP (Fix Pack) followed by a number, for example: 'DB2 v9.5.0.0' or 'DB2 v9.5.0.9'
    Affected if The installed Fix Pack is earlier than FP9 (FP1 through FP8 are vulnerable)
  3. Verify the operating system is UNIX
    Check the OS using 'uname -a' or check if running on Linux, AIX, Solaris, or HP-UX
    Affected if The system is a UNIX-based OS (Linux, AIX, Solaris, HP-UX) - the vulnerability only applies to UNIX systems
  4. Confirm IBM Tivoli Monitoring Agent presence
    Look for ITMA components in the DB2 installation directory, typically under the 'IBM/Tivoli' or 'Tivoli' subdirectory within the DB2 installation path
    Affected if IBM Tivoli Monitoring Agent is installed as part of the DB2 9.5 setup

A system is affected if it runs IBM DB2 version 9.5 on a UNIX platform with a Fix Pack earlier than 9 (FP1 through FP8) and has IBM Tivoli Monitoring Agent installed.

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 DB2 9.5 to Fix Pack 9 or later which contains the patched IBM Tivoli Monitoring Agent.

Fix this in Db2 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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