CVE-2024-35152
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 could allow an authenticated user to cause a denial of service with a specially crafted query due to improper memory allocation. IBM X-Force ID: 292639.
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 confidenceIBM Db2 version 11.5 contains a vulnerability where an authenticated user can craft a malicious query that triggers improper memory allocation, leading to a denial of service condition. The vulnerability requires the attacker to have valid database credentials to execute the specially crafted query.
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.8= 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.
-
Check installed IBM Db2 versionRun 'db2pd -db <database_name> -version' or 'db2level' command to retrieve the installed Db2 version numberAffected if The version shown is exactly 11.5.8 or 11.5.9 (exact match)
-
Confirm Db2 11.5 installationVerify that the product is IBM Db2 and the major version is 11.5 by checking the version outputAffected if The product is IBM Db2 version 11.5.x and specifically 11.5.8 or 11.5.9
-
Check for database connect privilegesQuery system catalog tables like SYSCAT.DBAUTH or use 'db2 get authorizations' to see which users have CONNECT privilege on the databaseAffected if Any non-admin user has CONNECT privilege and can execute queries against the database
You are affected if IBM Db2 version 11.5.8 or 11.5.9 is installed AND users with database connect privileges can execute arbitrary SQL queries.
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.
dbcve · scopedApply the IBM Db2 fix pack or patch for CVE-2024-35152. As an interim control, restrict database query privileges and monitor for unusual query patterns from authenticated users.
IBM Db2 11.5.10 or later
- 1. Back up the current Db2 database before performing any upgrade.
- 2. Verify current Db2 version by running: db2level
- 3. Download IBM Db2 11.5.10 or later from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
- 4. Stop all Db2 instances and services: db2stop force
- 5. Install the new version following IBM's installation documentation for your operating system
- 6. Update Db2 instances to the new version using db2iupdt command
- 7. Restart Db2 services and verify the instance is running: db2start
- 8. Validate the fix by running: db2level to confirm version 11.5.10 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-35152 — 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-35152 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