dbcve.org
Cognos AnalyticsApplication · Ibm

CVE-2024-51466

CRITICAL · 9.0 CVSS v3.1 Published 2024-12-20
Fix available
A fix is available. Upgrade to 11.2.4 / 12.0.4 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
IBM Cognos Analytics 11.2.0 through 11.2.4 FP4 and 12.0.0 through 12.0.4 is vulnerable to an Expression Language (EL) Injection vulnerability. A remote attacker could exploit this vulnerability to expose sensitive information, consume memory resources, and/or cause the server to crash when using a specially crafted EL statement.

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

A detailed technical summary for this CVE is being prepared.

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
Cognos AnalyticsApplication
Affected:>= 11.2.0, < 11.2.4>= 12.0.0, < 12.0.4= 11.2.4= 12.0.4

CVSS 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 11.2.4 / 12.0.4 or later
Fixed in 11.2.412.0.4
Vendor patch www.ibm.com →
Recommended fix Moderate confidence

IBM Cognos Analytics 11.2.4 FP5 or later for 11.2.x releases; IBM Cognos Analytics 12.0.5 or later for 12.0.x releases

  1. 1. Review the IBM support page at https://www.ibm.com/support/pages/node/7179496 for the specific patch/download corresponding to your installed version
  2. 2. Identify your current IBM Cognos Analytics version (11.2.x or 12.0.x)
  3. 3. Download the appropriate fixed version from IBM Fix Central or the support page
  4. 4. Back up your existing Cognos Analytics configuration and data
  5. 5. Apply the IBM fix following the vendor's installation instructions
  6. 6. Verify the patch was applied successfully by checking the Cognos Analytics version information
  7. 7. Test critical reporting and dashboard functionality to ensure normal operation
Caveat Review IBM release notes for potential configuration or migration changes between minor versions before applying the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51466 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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