dbcve.org
Db2Application · Ibm

CVE-2013-6744

HIGH · 8.5 CVSS v2.0 Published 2014-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
The Stored Procedure infrastructure in IBM DB2 9.5, 9.7 before FP9a, 10.1 before FP3a, and 10.5 before FP3a on Windows allows remote authenticated users to gain privileges by leveraging the CONNECT privilege and the CREATE_EXTERNAL_ROUTINE authority.

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 on Windows contains a privilege escalation vulnerability in its Stored Procedure infrastructure. Remote authenticated users with both CONNECT privilege and CREATE_EXTERNAL_ROUTINE authority can create malicious external stored procedures to elevate their privileges beyond what they should have.

MitigationUpgrade DB2 to version 9.7 FP9a, 10.1 FP3a, 10.5 FP3a or later. Alternatively, audit and restrict the CREATE_EXTERNAL_ROUTINE authority to only essential personnel until patching can be completed.

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.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.7.0.7= 9.7.0.8= 9.7.0.9= 10.1

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

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

  1. Determine installed DB2 version
    Run 'db2level' from the DB2 command window or check the Windows registry under HKLM\SOFTWARE\IBM\DB2\InstalledCopies
    Affected if The version shown is 9.5, 9.7 any fix pack, or 10.1 (before FP3a)
  2. Confirm Windows platform
    Verify the operating system is Windows; this vulnerability only affects DB2 on Windows
    Affected if DB2 is running on Windows and the version is among the affected versions listed
  3. Check if external stored procedures are allowed
    Query DB2 with: SELECT * FROM SYSCAT.ROUTINES WHERE ROUTINETYPE='E' AND VALID='Y'; or check if the EXTERNAL routine feature is enabled in DB2 configuration
    Affected if External stored procedures (ROUTINETYPE='E') exist in the database and are marked as valid
  4. Identify users with CREATE_EXTERNAL_ROUTINE authority
    Run: SELECT GRANTEE, AUTHIDTYPE FROM SYSCAT.DBAUTH WHERE EXTERNALROUTINEAUTH='Y'; to list all users granted this authority
    Affected if More than one user or any non-administrator account has CREATE_EXTERNAL_ROUTINE authority (Y)
  5. Check for users with CONNECT privilege
    Run: SELECT GRANTEE, AUTHIDTYPE FROM SYSCAT.DBAUTH WHERE CONNECTAUTH='Y'; to list users with CONNECT privilege
    Affected if The same user or users with CREATE_EXTERNAL_ROUTINE also have CONNECT privilege

You are affected if running DB2 9.5, 9.7 (any FP), or 10.1 on Windows AND your database has users with both CONNECT privilege and CREATE_EXTERNAL_ROUTINE authority beyond the database administrator.

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

Upgrade DB2 to version 9.7 FP9a, 10.1 FP3a, 10.5 FP3a or later. Alternatively, audit and restrict the CREATE_EXTERNAL_ROUTINE authority to only essential personnel until patching can be completed.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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 locally
dbcve dependency scanner

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