dbcve.org
Cognos AnalyticsApplication · Ibm

CVE-2024-25053

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, and 12.0.2 is vulnerable to improper certificate validation when using the IBM Planning Analytics Data Source Connection. This could allow an attacker to spoof a trusted entity by interfering in the communication path between IBM Planning Analytics server and IBM Cognos Analytics server. IBM X-Force ID: 283364.

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 confidence

IBM Cognos Analytics fails to properly validate SSL/TLS certificates when connecting to IBM Planning Analytics data sources. This improper certificate validation allows an attacker positioned on the network path between the two servers to perform a man-in-the-middle (MITM) attack, intercepting or potentially modifying communications by presenting a fraudulent certificate that the application accepts due to insufficient validation checks.

MitigationEnsure IBM Cognos Analytics is updated to a patched version when available. Configure data source connections to enforce proper certificate validation and verify that trusted CA certificates are correctly configured for Planning Analytics connections.

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
Cognos AnalyticsApplication
Affected:= 11.2.0= 11.2.1= 11.2.2= 11.2.3= 11.2.4= 12.0.0= 12.0.1= 12.0.2

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Cognos Analytics version
    Check the installed version through the Cognos Configuration tool (Gateway URL) or by examining the installation directory for a version file. Alternatively, access the Cognos Analytics welcome page which displays the version number.
    Affected if The installed version matches 11.2.0, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, or 12.0.2.
  2. Determine if Planning Analytics data sources are configured
    Log into Cognos Analytics Administration console and navigate to the Data Sources tab. Review the list of configured data sources to identify any connections to IBM Planning Analytics.
    Affected if One or more data sources connecting to IBM Planning Analytics exist in the Cognos environment.
  3. Review data source connection security settings
    Edit each Planning Analytics data source configuration and inspect the SSL/TLS or security-related settings. Look for options controlling certificate validation, such as 'Validate SSL certificate' or 'Trust store' configuration.
    Affected if Certificate validation is disabled, set to optional, or the trusted CA configuration is missing or incomplete for Planning Analytics connections.
  4. Inspect Java trust store configuration
    Locate the Java keystore used by Cognos Analytics (typically in the installation directory under jre/lib/security/cacerts). Verify that the trust store contains the appropriate CA certificates for Planning Analytics connections.
    Affected if The trust store is empty, missing CA certificates, or contains only self-signed certificates without proper chain validation.

You are affected if your IBM Cognos Analytics version is 11.2.0-11.2.4 or 12.0.0-12.0.2 AND you have configured Planning Analytics data sources with certificate validation disabled or misconfigured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure IBM Cognos Analytics is updated to a patched version when available. Configure data source connections to enforce proper certificate validation and verify that trusted CA certificates are correctly configured for Planning Analytics connections.

Fix this in Cognos Analytics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25053 — 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-25053 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