CVE-2024-35136
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) federated server 10.5, 11.1, and 11.5 is vulnerable to denial of service with a specially crafted query under certain non default conditions. IBM X-Force ID: 291307.
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 10.5, 11.1, and 11.5 contain a denial of service vulnerability that can be triggered via specially crafted SQL queries when certain non-default configuration conditions are met. An authenticated attacker with the ability to execute federated queries could cause the Db2 server to become unavailable, requiring a restart to restore normal operation.
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>= 10.5.0, <= 10.5.11>= 11.1.4, <= 11.1.4.7>= 11.5.0, <= 11.5.9CVSS 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.
-
Confirm Db2 version is within affected rangeRun 'db2level' or 'db2pd -version' and compare the output version to: 10.5.0 through 10.5.11, 11.1.4 through 11.1.4.7, or 11.5.0 through 11.5.9Affected if The installed version falls within any of these three ranges
-
Verify if federated query support is enabledRun 'db2 get dbm cfg' and look for the FEDERATED parameter. Alternatively query 'SELECT * FROM SYSIBM.SYSDBMCFG WHERE NAME='FEDERATED''Affected if FEDERATED is set to YES, meaning federated query functionality is active
-
Check for federated data sources configuredRun 'SELECT * FROM SYSCAT.FEDERATEDDATASOURCES' or check if any nickname objects exist in the database using 'SELECT * FROM SYSCAT.TABLES WHERE TYPE='N''Affected if Any federated data sources or nicknames are defined in the database
-
Identify users with federated query privilegesQuery SYSCAT.DBAUTH or DB2AUTH table: 'SELECT GRANTEE, AUTHIDTYPE FROM SYSCAT.DBAUTH WHERE FEDERATE='Y' OR CREATEFEDERATED='Y''Affected if Multiple untrusted users or groups have FEDERATE or CREATEFEDERATED privileges granted
You are affected if your Db2 version is in the affected range AND federated queries are enabled (FEDERATED=YES) with untrusted users having federated query permissions.
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 appropriate IBM Db2 interim fix or cumulative update for versions 10.5, 11.1, and 11.5 as specified in IBM's security bulletin. Additionally, restrict federated query permissions to trusted users and review non-default configurations to minimize attack surface.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35136 — 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-2024-35136 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