CVE-2012-4826
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 · uneditedStack-based buffer overflow in the SQL/PSM (aka SQL Persistent Stored Module) Stored Procedure (SP) infrastructure in IBM DB2 9.1, 9.5, 9.7 before FP7, 9.8, and 10.1 might allow remote authenticated users to execute arbitrary code by debugging a stored procedure.
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 confidenceStack-based buffer overflow in IBM DB2's SQL/PSM (Persistent Stored Module) stored procedure debugging infrastructure allows remote authenticated users to execute arbitrary code by triggering the overflow through the stored procedure debugger.
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.7= 9.7.0.1= 9.7.0.2= 9.7.0.3= 9.7.0.4= 9.7.0.5= 9.7.0.6= 9.8= 10.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/A:C
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.
-
Check installed DB2 versionRun the command 'db2level' or query 'SELECT SERVICE_LEVEL FROM SYSIBMADM.SYSENVIRONMENT' to retrieve the exact version and fix pack level of your DB2 installation.Affected if The installed version is any of: 9.1, 9.5, 9.7 (any subversion including 9.7.0.1 through 9.7.0.6), 9.8, or 10.1.
-
Verify SQL/PSM debugger is enabledRun 'db2 get dbm cfg' and look for the 'diaglevel' database manager configuration parameter, or query the system catalog for debugging-related settings. Also check if the DB2 debugger listener is active on the typical debug port.Affected if The stored procedure debugger is active or configurable on the system.
-
Check remote debugging permissionsQuery the DB2 permissions system: run 'SELECT GRANTOR, GRANTEE, AUTHIDTYPE FROM SYSCAT.DBAUTH' to see who has DBADM or DEBUG privileges, and check if remote authentication is enabled in the database manager configuration.Affected if REMOTE_AUTHENTICATION is set to YES or any non-DENIED value, or if DEBUG privilege is granted to users other than DBAs.
-
Inspect debugger listener configurationCheck the database manager configuration for 'SVCENAME' (service name/port) and verify whether the debugger can accept remote connections. Use 'db2 get dbm cfg | grep -i debug' to find debug-related settings.Affected if The debugger is bound to a network-accessible port and accepts remote connections.
You are affected if your DB2 version is 9.1, 9.5, 9.7 (any subversion), 9.8, or 10.1 AND the SQL/PSM stored procedure debugger is enabled and accessible, especially over remote connections.
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 IBM DB2 fix packs (FP7 or later for v9.7; equivalent fixes for other affected versions) to patch the SQL/PSM stored procedure component. If patches are unavailable, disable stored procedure debugging for remote sessions and restrict debug permissions to essential personnel 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-2012-4826 — 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-2012-4826 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