CVE-2010-3195
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 · uneditedUnspecified vulnerability in IBM DB2 9.1 before FP9, 9.5 before FP6, and 9.7 before FP2 on Windows Server 2008 allows attackers to cause a denial of service (trap) via vectors involving "special group and user enumeration."
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 · moderate confidenceDenial of service vulnerability in IBM DB2 versions 9.1 before FP9, 9.5 before FP6, and 9.7 before FP2 on Windows Server 2008, triggered through special group and user enumeration vectors that cause a system trap.
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= 9.1= 9.5= 9.7CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed DB2 versionRun the command 'db2level' from a DB2 command prompt or check the DB2 installation directory for version informationAffected if The version displayed is 9.1, 9.5, or 9.7 (without knowing the fix pack level, the system may be vulnerable)
-
Determine DB2 fix pack levelRun 'db2level' and locate the fix pack number in the output. For v9.1, look for FP9 or higher; for v9.5, look for FP6 or higher; for v9.7, look for FP2 or higherAffected if The fix pack is below FP9 for v9.1, below FP6 for v9.5, or below FP2 for v9.7
-
Verify Windows Server 2008 platformRun 'winver' or check system properties to confirm the operating system is Windows Server 2008Affected if The operating system is Windows Server 2008 and the DB2 version/fix pack falls within the affected ranges
-
Check for exposed group and user enumerationExamine DB2 authentication and security settings to determine if remote users can trigger group and user enumeration queries against the databaseAffected if External or low-privilege users can enumerate DB2 groups and users without additional authentication controls
The environment is affected if DB2 versions 9.1 (pre-FP9), 9.5 (pre-FP6), or 9.7 (pre-FP2) are installed on Windows Server 2008 and group/user enumeration interfaces are accessible to trigger the system trap.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the appropriate DB2 fix packs (FP9 for v9.1, FP6 for v9.5, FP2 for v9.7) or later to address this vulnerability on Windows Server 2008 environments.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3195 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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