CVE-2020-4874 is a medium severity (CVSS 5.9) flaw in IBM Cognos Controller, which uses weaker cryptographic algorithms than expected and could let an attacker decrypt sensitive data. It affects 10.4.1, 10.4.2 and 11.0.0. IBM's fixes are 10.4.1 FP1, 10.4.2 FP3 and 11.0.1 FP2, with no workaround listed.
What's affected
- IBM Cognos Controller 10.4.1, 10.4.2 and 11.0.0.
- Fixed: upgrade 10.4.1 to 10.4.1 FP1, 10.4.2 to 10.4.2 FP3, and 11.0.0 to 11.0.1 FP2, per IBM's bulletin.
- IBM says its Controller on Cloud 11.x and 10.4.2.x environments were already updated. No workaround is listed.
The record scores it 5.9 (Medium) with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Open the Cognos Controller about or version information screen on the application server and read the version and fix pack level. Match it against the three affected releases above. IBM's bulletin is the authority for fix pack naming.
What to do now
- Find all Cognos Controller installations, including test copies.
- Record the version and fix pack on each.
- Download the matching fix pack from IBM and test it against your reporting and consolidation jobs.
- Apply it in production during a close calendar gap, since Controller is finance critical.
- After patching, review which secrets or data the product encrypts and whether stored values were exposed to untrusted readers.
After you patch, record the new version for IBM Cognos Controller in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The record maps this to CWE-327, use of a broken or risky cryptographic algorithm. The data is encrypted, but the scheme is weaker than it should be, so someone who obtains the protected data may be able to recover it.
The score reflects a high attack complexity: an attacker has to be positioned to see the protected data first. For finance systems that is a sensible reason to patch on a normal cycle, not an emergency. IBM tracks the issue as X-Force ID 190837.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Is this exploited in the wild?
The record does not mark it as a CISA Known Exploited Vulnerability, and the IBM bulletin I read does not report exploitation.
How do I find every place IBM Cognos Controller is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
- https://www.ibm.com/support/pages/node/7149876
- https://exchange.xforce.ibmcloud.com/vulnerabilities/190837
Last reviewed: 19 October 2026.