dbcve.org
Cognos ControllerApplication · Ibm

CVE-2024-28780

MEDIUM · 5.9 CVSS v3.1 Published 2025-02-19
Fix available
A fix is available. Upgrade to 11.0.1.4 or later.
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 Controller 11.0.0 through 11.0.1 FP3 and IBM Controller 11.1.0 Rich Client  uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

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 Controller versions 11.0.0-11.0.1 FP3 and 11.1.0 Rich Client implement weaker than expected cryptographic algorithms, potentially allowing an attacker to decrypt highly sensitive information stored or transmitted by the system.

MitigationApply vendor-provided security patches when available; if patches are unavailable, implement compensating controls such as additional encryption layers or data-at-rest encryption using stronger algorithms, and restrict access to sensitive data stores.

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 ControllerApplication
Affected:>= 11.0.0, < 11.0.1.4
ControllerApplication
Affected:= 11.1.0

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 Controller version
    Check the installed version through Windows Add/Remove Programs, or look for version information in the Cognos Controller installation directory, typically found in version.ini or about dialog within the application
    Affected if The version shown is 11.0.0 through 11.0.1.3 (any version below 11.0.1.4 within the 11.0.x line)
  2. Identify installed IBM Controller version
    Check the installed version through Windows Add/Remove Programs for IBM Controller 11.1.0, or look in the Controller installation directory for version information
    Affected if The installed version is exactly 11.1.0 (Rich Client variant)
  3. Verify exact version number via Cognos Configuration
    Open Cognos Configuration (cogconfig.exe) and navigate to the About section or Environment settings to confirm the precise build version number
    Affected if The version displayed is less than 11.0.1.4 in the 11.0.x line, or shows as 11.1.0
  4. Confirm product variant
    Determine whether the installation is Cognos Controller (web-based) or IBM Controller (Rich Client) by checking the installed program name and startup shortcuts
    Affected if The product is either IBM Cognos Controller versions 11.0.0-11.0.1 FP3 or IBM Controller version 11.1.0 Rich Client

You are affected if your installed IBM Cognos Controller version is 11.0.0 through 11.0.1.3 (any build before 11.0.1.4), or if you have IBM Controller version 11.1.0 Rich Client installed.

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.

dbcve · scoped
Upgrade available Upgrade to 11.0.1.4 or later
Fixed in 11.0.1.4
Interim mitigation

Apply vendor-provided security patches when available; if patches are unavailable, implement compensating controls such as additional encryption layers or data-at-rest encryption using stronger algorithms, and restrict access to sensitive data stores.

Recommended fix Moderate confidence

IBM Cognos Controller 11.0.1.4 or later (or IBM Controller 11.1.x if a later 11.1.x release exists beyond 11.1.0)

  1. 1. Identify the current IBM Cognos Controller version installed in your environment
  2. 2. Download IBM Cognos Controller 11.0.1.4 or later from IBM Fix Central (https://www.ibm.com/support/fixcentral)
  3. 3. Review IBM Cognos Controller installation documentation and release notes before upgrading
  4. 4. Perform a full backup of the Cognos Controller database and configuration files
  5. 5. Schedule an appropriate maintenance window for the upgrade
  6. 6. Run the installer for version 11.0.1.4 or later following IBM's standard upgrade procedures
  7. 7. Verify the installation completed successfully and the version number reflects the patched release
  8. 8. Test critical financial reporting and consolidation workflows to ensure functionality is intact
Caveat Review IBM release notes for 11.0.1.4 for any configuration or compatibility changes; minor version upgrades within the same major.minor release typically have low risk

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

Fix this in Cognos Controller Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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