dbcve.org
Db2Application · Ibm

CVE-2012-2194

MEDIUM · 5.0 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 →
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
Directory traversal vulnerability in the SQLJ.DB2_INSTALL_JAR stored procedure in IBM DB2 9.1 before FP12, 9.5 through FP9, 9.7 through FP6, 9.8 through FP5, and 10.1 allows remote attackers to replace JAR files via unspecified 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 · high confidence

A directory traversal vulnerability exists in the SQLJ.DB2_INSTALL_JAR stored procedure in IBM DB2 versions 9.1 before FP12, 9.5 through FP9, 9.7 through FP6, 9.8 through FP5, and 10.1. The vulnerability allows remote attackers to manipulate file paths and replace JAR files on the system via the stored procedure, potentially leading to code execution or integrity compromise.

MitigationApply the appropriate IBM DB2 Fix Pack (FP12 for v9.1, FP10 for v9.5, FP7 for v9.7, FP6 for v9.8, and FP2 for v10.1 or later) to address this vulnerability. Additionally, restrict database user privileges to prevent unauthorized access to the SQLJ.DB2_INSTALL_JAR stored procedure.

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
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

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. Check installed DB2 version and fix pack level
    Run the command `db2level` from a DB2 command prompt, or query `SELECT service_level, fixpack_num FROM SYSIBMADM.env_inst_info`. Compare the output against the vulnerable ranges: DB2 9.1 before FP12, 9.5 through FP9, 9.7 through FP6, 9.8 through FP5, and 10.1.
    Affected if The installed version falls within any of these vulnerable version ranges.
  2. Verify the SQLJ.DB2_INSTALL_JAR stored procedure exists
    Query the system catalog using: `SELECT PROCSCHEMA, PROCNAME FROM SYSCAT.PROCEDURES WHERE PROCSCHEMA = 'SQLJ' AND PROCNAME = 'DB2_INSTALL_JAR'`.
    Affected if The stored procedure exists in the database.
  3. Check execute privileges on the vulnerable stored procedure
    Query privilege information using: `SELECT GRANTEE, PROCSCHEMA, PROCNAME, EXECUTEAUTH FROM SYSCAT.PROCAUTH WHERE PROCSCHEMA = 'SQLJ' AND PROCNAME = 'DB2_INSTALL_JAR'`. Review which database users or groups have EXECUTE permission.
    Affected if Users other than DBADMIN or privileged administrators have EXECUTE permission on SQLJ.DB2_INSTALL_JAR.
  4. Confirm JDBC or SQLJ applications can invoke the stored procedure
    Review application configurations and database connection settings to determine if non-admin applications have the ability to call stored procedures. Check if applications connect with IDs that have been granted execute access to the SQLJ schema.
    Affected if Applications connect with database IDs that have execute rights on the SQLJ.DB2_INSTALL_JAR procedure.

A user is affected if their DB2 version matches one of the vulnerable release ranges AND the SQLJ.DB2_INSTALL_JAR stored procedure is accessible to users with insufficient 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, FP10 for v9.5, FP7 for v9.7, FP6 for v9.8, and FP2 for v10.1 or later) to address this vulnerability. Additionally, restrict database user privileges to prevent unauthorized access to the SQLJ.DB2_INSTALL_JAR stored procedure.

Fix this in Db2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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