CVE-2011-0731
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 · uneditedBuffer overflow in the DB2 Administration Server (DAS) component in IBM DB2 9.1 before FP10, 9.5 before FP7, and 9.7 before FP3 on Linux, UNIX, and Windows allows remote attackers to execute arbitrary code 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 confidenceBuffer overflow vulnerability in IBM DB2's Administration Server (DAS) component allows remote attackers to execute arbitrary code via unspecified vectors. The DAS handles administrative operations for DB2 and is accessible over network ports on Linux, UNIX, and Windows platforms.
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.1<= 9.5= 9.5<= 9.7= 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 DB2 installation and versionRun 'db2level' or 'db2pd -version' from a DB2 instance owner account to determine the installed DB2 version and fix pack levelAffected if The version displayed is 9.1, 9.5, or 9.7 (any fix pack below FP10 for v9.1, FP7 for v9.5, or FP3 for v9.7)
-
Determine if DAS is installed and runningExecute 'db2admin' or 'db2set -all' to check DAS configuration; on Windows check the DB2 Administration Server service, on UNIX/Linux check for the 'db2ad' processAffected if The Administration Server (DAS) is installed and running on the system
-
Check DAS network listener configurationExamine the DB2 configuration parameters using 'GET DBM CFG' or check the services file for port 523 (default DAS port) to determine if DAS is listening on a network interfaceAffected if DAS is configured to listen on a network interface accessible from non-localhost addresses (not bound to 127.0.0.1 only)
-
Verify network exposure of DAS portUse 'netstat -an | grep 523' or 'lsof -i :523' to confirm which IP addresses the DAS port is bound to, and review any firewall rules or TCP wrappers configurationAffected if The DAS port (default 523) is bound to 0.0.0.0 or an external IP address rather than localhost only
You are affected if DB2 version is 9.1 (before FP10), 9.5 (before FP7), or 9.7 (before FP3) AND the Administration Server is running and network-accessible.
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 relevant DB2 Fix Pack (FP10 for v9.1, FP7 for v9.5, FP3 for v9.7) to address the buffer overflow. Additionally, restrict network access to the DAS to authorized administrators only.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0731 — 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-2011-0731 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