dbcve.org
Db2Application · Ibm

CVE-2012-2197

HIGH · 7.1 CVSS v2.0 Published 2012-07-25
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
Remotely reachable 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
Stack-based buffer overflow in the Java Stored Procedure infrastructure in IBM DB2 9.1 before FP12, 9.5 through FP9, 9.7 through FP6, 9.8 through FP5, and 10.1 allows remote authenticated users to execute arbitrary code by leveraging certain CONNECT and EXECUTE privileges.

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

Stack-based buffer overflow in the Java Stored Procedure infrastructure in IBM DB2 allows remote authenticated users with CONNECT and EXECUTE privileges to execute arbitrary code via specially crafted Java stored procedure calls.

MitigationApply the appropriate IBM DB2 Fix Pack (FP12 for v9.1, FP9 for v9.5, FP6 for v9.7, FP5 for v9.8, and vendor-supplied fix for v10.1) to address the vulnerability.

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.1= 9.1.0.1= 9.1.0.2= 9.1.0.3= 9.1.0.4= 9.1.0.5= 9.1.0.6= 9.1.0.7= 9.1.0.8= 9.1.0.9= 9.1.0.10= 9.1.0.11

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/Au:S/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 DB2 version
    Run 'db2level' or 'db2pd -version' from the DB2 instance owner account
    Affected if Version shows 9.1.x (any fix pack 0-11)
  2. Confirm Java Stored Procedure feature is in use
    Query the system catalog: SELECT PROCNAME FROM SYSCAT.PROCEDURES WHERE LANGUAGE='JAVA'
    Affected if Any Java stored procedures exist in the database
  3. Check for users with CONNECT privilege
    Run 'db2 get authorizations' or query SYSCAT.DBAUTH with CONNECT privilege
    Affected if Any database users or groups have CONNECT privilege granted
  4. Check for users with EXECUTE privilege on procedures
    Query SYSCAT.PROCAUTH or run 'db2advisor' to list procedure Execute privileges
    Affected if Any users have EXECUTE privilege on stored procedures

Affected if running DB2 version 9.1.x and Java stored procedures are present with users having both CONNECT and EXECUTE privileges.

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 DB2 Fix Pack (FP12 for v9.1, FP9 for v9.5, FP6 for v9.7, FP5 for v9.8, and vendor-supplied fix for v10.1) to address the vulnerability.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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