dbcve.org
Db2Application · Ibm

CVE-2010-3197

MEDIUM · 5.0 CVSS v2.0 Published 2010-08-31
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
IBM DB2 9.7 before FP2 does not perform the expected access control on the monitor administrative views in the SYSIBMADM schema, which allows remote attackers to obtain sensitive information 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

IBM DB2 9.7 before Fix Pack 2 fails to enforce proper access controls on monitor administrative views within the SYSIBMADM schema, allowing unauthenticated remote attackers to potentially view sensitive system monitoring information that should be restricted.

MitigationUpgrade IBM DB2 to version 9.7 Fix Pack 2 or later to apply the access control patches for the SYSIBMADM schema views.

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.7

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

AV:N/AC:L/Au:N/C:P/I:N/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
    Run the command: db2level or execute: SELECT GET_VENDOR_VERSION, VERSION() AS VERSION FROM SYSIBM.SYSDUMMY1
    Affected if The version displayed is not 9.7 (then not affected)
  2. Confirm DB2 version is 9.7
    Examine the version output from step 1 - look for version number 9.7 in the output
    Affected if The version does not show 9.7 (then not affected)
  3. Check Fix Pack level
    Run db2level and look for the Fix Pack or Fix Pack number in the output (for example, 'Fix Pack 2', 'FP2', or similar)
    Affected if The output shows Fix Pack 1, no Fix Pack number, or a version earlier than Fix Pack 2 (this means the environment is affected)
  4. Verify SYSIBMADM schema accessibility
    Connect to the database and attempt to query a SYSIBMADM view, for example: SELECT * FROM SYSIBMADM.SNAPDB or SELECT * FROM SYSIBMADM.MON_GET_CONNECTION
    Affected if Queries execute successfully without proper authentication or authorization errors (indicates the vulnerable access control state)

The environment is affected if running DB2 version 9.7 without Fix Pack 2 or later applied, as the access controls on SYSIBMADM schema views are not properly enforced in earlier versions.

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 to version 9.7 Fix Pack 2 or later to apply the access control patches for the SYSIBMADM schema views.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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