dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2024-28795

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

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 InfoSphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 286832.

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 InfoSphere Information Server 11.7 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed malicious JavaScript code into the interface, which executes in the browsers of other users viewing the affected content, potentially stealing session credentials or performing actions on behalf of authenticated users.

MitigationApply IBM patches when available. In the interim, implement output encoding for all user-supplied data displayed in the Web UI and configure strict Content-Security-Policy headers to mitigate XSS execution.

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
Infosphere Information ServerApplication
Affected:= 11.7

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify installed IBM InfoSphere Information Server version
    Locate and verify the installed version of IBM InfoSphere Information Server in your environment. Use the system inventory, version lookup tool, or product-specific command provided by IBM to determine the exact version number currently deployed.
    Affected if The installed version is 11.7 exactly (the only affected version per vendor advisory).
  2. Confirm Web UI component is enabled
    Determine whether the Web UI component for IBM InfoSphere Information Server is enabled and accessible in your environment. Check the service configuration, administration console, or startup scripts to verify the Web UI is running.
    Affected if The Web UI is enabled and accessible to users, providing an attack surface for XSS injection.
  3. Locate user-supplied input fields in the Web UI
    Review the Web UI interface for fields that accept and store user input, such as name fields, description boxes, comments, or metadata entries. These are potential injection points for stored XSS.
    Affected if The Web UI contains input fields that store and display user-supplied data to other users.
  4. Inspect stored data for suspicious script content
    Examine stored data within the application database or content repositories for any existing malicious JavaScript tags, script elements, or event handler attributes that may have been injected. Query user-contributed fields for patterns like <script, javascript:, onload, onerror, or similar XSS vectors.
    Affected if Stored data contains embedded JavaScript or HTML that could execute in user browsers, indicating active exploitation or prior injection.

You are affected if IBM InfoSphere Information Server version 11.7 is installed, the Web UI is enabled, and user-supplied input fields are present that could accept and store malicious script content.

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

Apply IBM patches when available. In the interim, implement output encoding for all user-supplied data displayed in the Web UI and configure strict Content-Security-Policy headers to mitigate XSS execution.

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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