CVE-2024-37071
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) 10.5, 11.1, and 11.5 could allow an authenticated user to cause a denial of service with a specially crafted query due to improper memory allocation.
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 improper memory allocation in the query processing component. An authenticated database user can send a specially crafted query that triggers faulty memory handling, causing the Db2 server to crash and result in 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>= 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.
-
Check installed Db2 versionRun command: `db2level` or `db2pd -version` from a Db2 command line. Alternatively, query `SYSPROC.GET_DBM_CFG` or check the installation directory for version files.Affected if The installed version falls within 10.5.0-10.5.11, 11.1.4-11.1.4.7, or 11.5.0-11.5.9.
-
Confirm query processing component is activeVerify the Db2 instance is running and accepting connections. Run: `db2 list database directory` and `db2 connect to <database>`. Query processing is enabled by default for any active database.Affected if The Db2 instance is running and databases are accessible for user connections.
-
Identify authenticated users with query execution permissionsRun: `db2 connect to <database>` then `db2 select grantor, grantee, timetype from syscat.dbauth` or `db2 get authorizations`. Check for non-admin users with CONNECT and DBADM privileges.Affected if There are authenticated users other than admins who can execute SQL queries against the database.
-
Verify crash conditions are presentReview Db2 diagnostic logs (db2diag.log) for recent crash events or signal 6 errors. Run: `db2diag -A` or check `/<instance_home>/sqllib/db2dump/db2diag.log`.Affected if Recent crashes or memory allocation errors appear in diagnostic logs related to query processing.
You are affected if your Db2 version is 10.5.0-10.5.11, 11.1.4-11.1.4.7, or 11.5.0-11.5.9 AND the database accepts authenticated user connections that can execute 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.
From vendor dataApply IBM's security patch for this vulnerability to all affected Db2 instances. As an interim control, audit and restrict database user permissions to limit query execution to trusted accounts until the patch is deployed.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37071 — 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-37071 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