dbcve.org
Db2Application · Ibm

CVE-2007-3676

HIGH · 10.0 CVSS v2.0 Published 2008-02-13
Fix available
A fix is available. Upgrade to after 9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Universal Database (UDB) Administration Server (DAS) 8 before Fix Pack 16 and 9 before Fix Pack 4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via modified pointer values in unspecified remote administration requests, which triggers memory corruption or other invalid memory access. NOTE: this might be the same issue as CVE-2008-0698.

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
How this class of weakness works · CWE-399

A legacy NVD category grouping weaknesses in how resources — memory, file handles, connections — are allocated, used, and released. It gathers leaks, exhaustion, and lifecycle bugs under one label rather than naming a single flaw. The fix depends on the specific resource issue, generally pairing acquisition with release and bounding what any request can consume.

General guidance for the resource management errors class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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

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

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.0
Vendor patch labs.idefense.com →
Recommended fix High confidence

DB2 v8 Fix Pack 16+ or DB2 v9 Fix Pack 4+

  1. Identify the current DB2 version and Fix Pack level using 'db2level' command
  2. Download the appropriate Fix Pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  3. For DB2 v8: Upgrade to Fix Pack 16 or later
  4. For DB2 v9: Upgrade to Fix Pack 4 or later
  5. Stop all DB2 instances and DAS before applying the Fix Pack
  6. Apply the Fix Pack following IBM's installation instructions
  7. Restart DB2 instances and verify the fix with 'db2level'
  8. Test critical database operations to ensure stability
Caveat Review IBM DB2 Fix Pack release notes for version-specific changes before upgrading; test in non-production environment first

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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