dbcve.org
Db2Application · Ibm

CVE-2008-4692

HIGH · 10.0 CVSS v2.0 Published 2008-10-22
Fix available
A fix is available. Upgrade to after 9.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Native Managed Provider for .NET component in IBM DB2 8 before FP17, 9.1 before FP6, and 9.5 before FP2, when a definer cannot maintain objects, preserves views and triggers without marking them inoperative or dropping them, which has unknown impact and attack 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

IBM DB2's Native Managed Provider for .NET fails to properly handle views and triggers when the definer (owner) cannot maintain their objects. Instead of marking these objects inoperative or dropping them, the system preserves them, potentially allowing orphaned or unauthorized database objects to persist with elevated privileges.

MitigationUpgrade IBM DB2 to the fixed version (v8 FP17, v9.1 FP6, or v9.5 FP2 or later) and audit existing views and triggers for proper ownership and validity.

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:<= 8.0<= 9.1<= 9.5= 8.0= 9.1= 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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/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. Identify installed DB2 version
    Run command: db2pd -version or query SELECT * FROM SYSIBM.SYSVERSION. Alternatively, connect to the database and run: db2 SELECT SERVICE_LEVEL FROM SYSIBM.SYSENVIRONMENT
    Affected if The version is DB2 v8.0 or earlier, v9.1 or earlier, or v9.5 or earlier (including all fix packs below FP17 for v8, FP6 for v9.1, and FP2 for v9.5)
  2. Query for views with potentially orphaned ownership
    Run: db2 SELECT VIEWNAME, VIEW_SCHEMA, CREATE_TIME FROM SYSCAT.VIEWS WHERE VIEW_SCHEMA NOT IN (SELECT GRANTOR FROM SYSCAT.DBAUTH) OR VIEW_SCHEMA NOT IN (SELECT GRANTEE FROM SYSCAT.DBAUTH)
    Affected if Views exist where the owner (VIEW_SCHEMA) no longer has database privileges or user authority to maintain those objects
  3. Query for triggers with potentially orphaned ownership
    Run: db2 SELECT TRIGNAME, TRIG_SCHEMA, CREATE_TIME FROM SYSCAT.TRIGGERS WHERE TRIG_SCHEMA NOT IN (SELECT GRANTOR FROM SYSCAT.DBAUTH) OR TRIG_SCHEMA NOT IN (SELECT GRANTEE FROM SYSCAT.DBAUTH)
    Affected if Triggers exist where the owner (TRIG_SCHEMA) no longer has database privileges or user authority to maintain those objects
  4. Check for inoperative views
    Run: db2 SELECT VIEWNAME, VIEW_SCHEMA, STATUS FROM SYSCAT.VIEWS WHERE STATUS = 'I'
    Affected if Any views are marked with STATUS 'I' (inoperative), which indicates the underlying objects they depend on may have changed
  5. Audit views and triggers with elevated privileges
    Run: db2 SELECT V.VIEWNAME, V.VIEW_SCHEMA, V.CREATE_TIME FROM SYSCAT.VIEWS V JOIN SYSCAT.DBAUTH D ON V.VIEW_SCHEMA = D.GRANTEE WHERE D.SYSTEMAUTH = 'Y' OR DBADM = 'Y'
    Affected if Views exist that are owned by users with system administrative privileges (SYSTEMAUTH='Y' or DBADM='Y'), which could persist with elevated access if the owner loses maintainer status

If the installed DB2 version is v8.0, v9.1, v9.5 or any earlier version (including all fix packs below FP17, FP6, and FP2 respectively), and views or triggers exist owned by users who no longer have authority to maintain those objects, the environment is affected by this vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 9.5
Interim mitigation

Upgrade IBM DB2 to the fixed version (v8 FP17, v9.1 FP6, or v9.5 FP2 or later) and audit existing views and triggers for proper ownership and validity.

Recommended fix High confidence

DB2 8 FP17+, DB2 9.1 FP6+, or DB2 9.5 FP2+

  1. Identify current DB2 version and fix pack level using 'db2level' command
  2. For DB2 8.x: Upgrade to Fix Pack 17 or later
  3. For DB2 9.1: Upgrade to Fix Pack 6 or later
  4. For DB2 9.5: Upgrade to Fix Pack 2 or later
  5. After upgrading, verify the fix pack level is correct using 'db2level'
  6. Test applications using the Native Managed Provider for .NET to ensure functionality
Caveat These are very old DB2 versions (2008 era) that may be end-of-life; test thoroughly for compatibility issues after upgrade, especially with .NET applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Db2 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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