dbcve.org
Db2Application · Ibm

CVE-2012-0710

MEDIUM · 5.0 CVSS v2.0 Published 2012-03-20
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.1 before FP11, 9.5 before FP9, 9.7 before FP5, and 9.8 before FP4 allows remote attackers to cause a denial of service (daemon crash) via a crafted Distributed Relational Database Architecture (DRDA) request.

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 versions 9.1, 9.5, 9.7, and 9.8 contain a denial of service vulnerability in the Distributed Relational Database Architecture (DRDA) protocol handler. Remote attackers can send specially crafted DRDA requests that cause the DB2 daemon to crash, resulting in service interruption.

MitigationApply the appropriate IBM DB2 fix packs (FP11 for v9.1, FP9 for v9.5, FP5 for v9.7, FP4 for v9.8) or later versions to address this vulnerability. Until patches are applied, restrict network access to DB2 listen ports using firewalls or network segmentation.

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.5= 9.7= 9.8

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

Work through these to decide whether this CVE applies to you.

  1. Identify installed DB2 version
    Run the command 'db2level' from a DB2 instance owner account or check the output of 'db2pd -version'
    Affected if Version reported is 9.1, 9.5, 9.7, or 9.8 (without the corresponding fix pack)
  2. Verify DRDA protocol listener is active
    Run 'db2pd -dbptmpin' or check DB2 configuration for the service name/port using 'get dbm cfg | grep SVCENAME' then verify the port is listening with 'netstat -an | grep <port>'
    Affected if DB2 is listening on a DRDA port (typically 50000 or configured SVCENAME) and responds to connections
  3. Confirm network exposure of DB2 port
    Check firewall rules or DB2 configuration parameter 'DISCOVER_INST' using 'get dbm cfg' and review whether the listener binds to exposed interfaces versus localhost only
    Affected if DB2 listener port is bound to 0.0.0.0 or an IP address accessible from untrusted networks, or firewall permits external access to the DB2 port

You are affected if you run DB2 version 9.1, 9.5, 9.7, or 9.8 without the corresponding fix packs AND your DRDA listener is network-accessible.

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 packs (FP11 for v9.1, FP9 for v9.5, FP5 for v9.7, FP4 for v9.8) or later versions to address this vulnerability. Until patches are applied, restrict network access to DB2 listen ports using firewalls or network segmentation.

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-0710 — 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-0710 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