CVE-2024-41752
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 Cognos Analytics 11.2.0 through 11.2.4 and 12.0.0 through 12.0.3 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.
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 · high confidenceIBM Cognos Analytics versions 11.2.0-11.2.4 and 12.0.0-12.0.3 contains an HTML injection vulnerability where a remote attacker can inject malicious HTML code into user-facing fields. When victims view this crafted content, the injected HTML executes within the security context of the hosting site, potentially leading to session hijacking, credential theft, or defacement.
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>= 11.2.0, <= 11.2.4>= 12.0.0, <= 12.0.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Cognos Analytics versionAccess the IBM Cognos Analytics administration console or check the product 'About' information panel. The version is typically displayed in the Cognos Configuration utility or can be retrieved via the /bi/v1/disp URl or help/about page.Affected if The installed version is 11.2.0 through 11.2.4, or 12.0.0 through 12.0.3 (inclusive).
-
Confirm user-facing input fields existLocate user-facing fields where content can be entered and saved, such as report descriptions, dashboard titles, folder names, user profile fields, or custom report prompts.Affected if User-facing input fields exist that accept free-form text without apparent sanitization.
-
Test for lack of HTML sanitization on input fieldsAttempt to insert a benign HTML tag such as <b>test</b> or <script>alert(1)</script> into a user-facing field, then view the rendered output to see if HTML is executed or stripped.Affected if The injected HTML is rendered as-is in the browser rather than being encoded or stripped.
-
Check for Content Security Policy headersInspect HTTP response headers from the IBM Cognos server using browser developer tools or a command-line tool like curl to check for Content-Security-Policy header.Affected if No CSP header is present, or CSP does not include 'unsafe-inline' restrictions that would block injected scripts.
You are affected if your IBM Cognos Analytics version falls within 11.2.0-11.2.4 or 12.0.0-12.0.3 AND user-facing input fields render HTML without sanitization.
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.
dbcve · scopedUpgrade to a patched version of IBM Cognos Analytics once available. Until then, implement strict input validation and output encoding on all user-controllable fields, and consider deploying Content Security Policy (CSP) headers to mitigate client-side code execution.
IBM Cognos Analytics 11.2.5 or later, or 12.0.4 or later
- Identify the current installed version of IBM Cognos Analytics (11.2.x or 12.0.x)
- Determine which version line (11.2 or 12.0) is currently in use
- Download IBM Cognos Analytics version 11.2.5 or later from IBM Fix Central or Passport Advantage
- Alternatively, download version 12.0.4 or later if using the 12.0.x line
- Review IBM installation documentation for upgrade prerequisites
- Perform a full backup of the existing Cognos Analytics environment, including configuration files and content store database
- Stop all Cognos Analytics services before applying the upgrade
- Install the upgraded version following IBM's standard upgrade procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41752 — 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-41752 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