CVE-2024-52903
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 12.1.0 and 12.1.1 is vulnerable to a denial of service as the server may crash under certain conditions with a specially crafted query.
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 and 12.1.1 for Linux, UNIX, and Windows contain a vulnerability where a specially crafted query can cause the database server to crash, resulting in denial of service. The vulnerability is exploitable remotely via query input without authentication details explicitly mentioned.
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>= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify IBM Db2 is installedRun the 'db2level' command or 'db2pd -version' from a Db2 instance owner account. On Linux/UNIX, you can also check for the presence of the Db2 installation directory (typically under /opt/ibm/db2 or /opt/IBM).Affected if The commands execute successfully and return IBM Db2 version information, confirming Db2 is installed.
-
Determine the installed Db2 versionExecute 'db2level' and parse the output for the version number. The output format typically shows version, release, and modification level (for example: 12.1.0.0 or 12.1.1.0).Affected if The version output shows a version number of 12.1.0.x or 12.1.1.x.
-
Confirm the version is within affected rangeCompare the extracted version (first two octets) against the affected range: versions 12.1.0 and 12.1.1. Note that subversions like 12.1.0.0 through 12.1.1.9 are all included in the affected range.Affected if The installed version is 12.1.0 or 12.1.1 (any subversion within these major.minor releases).
-
Check if remote query access is enabledExamine Db2 configuration parameters 'DBM CFG' for 'TCP/IP Service Name' and 'LISTENER' settings, or review network exposure via 'db2 get dbm cfg'. Also verify if TCP/IP listening is active.Affected if TCP/IP protocol is enabled and the database is accessible over the network, as the vulnerability is exploitable remotely via query input.
If IBM Db2 version 12.1.0 or 12.1.1 is installed and remote network access is enabled, the environment is affected by this vulnerability.
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 fix pack or interim fix from IBM's support portal. Prior to deployment, test the patch in a non-production environment and schedule appropriate maintenance downtime.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52903 — 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-52903 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