CVE-2025-1992
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) 11.5.0 through 11.5.9 and 12.1.0 through 12.1.1 could allow an authenticated user in federation environment, to cause a denial of service due to insufficient release of allocated memory after usage.
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 11.5.0-11.5.9 and 12.1.0-12.1.1 contain a memory leak in the federation component. An authenticated user in a federation environment can repeatedly trigger the leak by executing queries through federated tables, causing memory to accumulate without proper deallocation, eventually leading to denial of service.
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>= 11.5.0, <= 11.5.9= 12.1.0= 12.1.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
- 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.
-
Check installed Db2 versionRun 'db2level' or query 'select * from sysibmadm.env_inst_info' to obtain the installed version and fix pack level.Affected if The version is 11.5.0 through 11.5.9, or exactly 12.1.0 or 12.1.1.
-
Verify federation feature is enabledRun 'db2set -all' and look for DB2_FEDERATION in the output, or check the database manager configuration with 'db2 get dbm cfg' for federation-related parameters.Affected if DB2_FEDERATION is set to YES or federation is otherwise active in the Db2 instance.
-
Identify federated tables in the databaseQuery the catalog: 'select tabname, tabschema from syscat.tables where type = 'N'' for nicknames, or check SYSCAT.SERVERS for federated data sources.Affected if Any nicknames or federated data sources exist in the database.
-
Monitor federation-related memory consumptionUse 'db2pd -db <dbname> -mempool' to examine memory pool usage, focusing on the db2fmp process or federation-related memory heaps.Affected if Memory pools show continuous growth or abnormally high memory usage that does not release after query completion.
-
Check for active federation queriesRun 'db2 list applications' or 'db2 get snapshot for dynamic sql' to identify queries hitting federated tables (nicknames).Affected if Queries against federated tables are executing and memory consumption is increasing over time.
You are affected if your Db2 version falls within 11.5.0-11.5.9 or 12.1.0-12.1.1 AND federation is enabled with federated objects in use, and you observe unusual memory growth during federation query execution.
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's official patches for this vulnerability. In the interim, restrict federation access to only trusted authenticated users and monitor Db2 memory consumption for anomalies.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1992 — 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-1992 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