Db2Application · Ibm
CVE-2025-14689
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 · uneditedIBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 12.1.0 through 12.1.3 could allow an authenticated user to cause a denial of service due to improper neutralization of special elements in data query logic with federated objects.
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 · moderate confidenceIBM Db2 versions 12.1.0 through 12.1.3 contain a vulnerability in the federated objects query logic where improper neutralization of special elements allows an authenticated user to inject specially crafted queries that cause a denial of service condition.
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
>= 12.1.0, <= 12.1.3CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 installed Db2 versionRun 'db2pd -db <database_name> -version' or check 'db2level' command output to retrieve the Db2 version numberAffected if Version is 12.1.0, 12.1.1, 12.1.2, or 12.1.3 (within the range 12.1.0 to 12.1.3)
-
Confirm federated feature is enabledCheck Db2 configuration for federated database settings. Query SYSIBM.SYSCAT.SERVERS or run 'db2pd -db <db> -federated' to see if the federated database option is activeAffected if Federated database functionality is enabled or configured on the Db2 instance
-
Check for existing federated objectsQuery the catalog tables SYSIBM.SYSCAT.SERVERS, SYSIBM.SYSCAT.USEROPTIONS, or use 'LIST WRAPPER' and 'LIST SERVER' commands to list configured federated wrappers and data sourcesAffected if Any federated servers, wrappers, or nicknames are defined in the database
-
Verify authenticated user access to federated queriesReview user permissions on federated objects using 'db2 grant' statements or check SYSIBM.SYSCAT.DBAUTH and SYSIBM.SYSCAT.TABAUTH for federated object privilegesAffected if Untrusted authenticated users have permissions to create or execute federated queries
The environment is affected if Db2 version is 12.1.0 through 12.1.3 AND the federated database feature is enabled with federated objects accessible to authenticated users.
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 patches or upgrade to a version beyond 12.1.3 when available. Restrict federated object permissions for untrusted authenticated users until patched.
Fix this in Db2
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14689 — 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-2025-14689 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