dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2024-28797

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 stored 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: 287136.

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 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 that persists in the application, executing within browsers of other users who view the affected content, potentially exposing session credentials.

MitigationApply IBM patches when available; implement output encoding and input validation for all user-supplied data in the Web UI; consider implementing 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. Confirm IBM InfoSphere Information Server installation
    Locate the installation directory or check system services for InfoSphere Information Server components. Common paths include C:\IBM\InformationServer on Windows or /opt/IBM/InformationServer on Linux. Look for executable files or services named 'InformationServer' or related components.
    Affected if The product is installed and the Web UI component is accessible to users
  2. Identify installed version
    Check the version of IBM InfoSphere Information Server by examining version files in the installation directory, checking the IBM installation manager, or querying the product via its administrative console. Look for a file named version.txt, about.html, or use the 'imcl listInstalledPackages' command if IBM Installation Manager is available.
    Affected if The installed version is exactly 11.7
  3. Verify Web UI is enabled
    Confirm the Web UI component is accessible by accessing the IBM InfoSphere Information Server administration console through a browser. Typically accessed via http://hostname:port/ibm/console or similar URL pattern depending on installation configuration. Check if the login page loads successfully.
    Affected if The Web UI is accessible and users can authenticate to it
  4. Check for suspicious stored content
    Review the Web UI for any user-contributed fields that accept input and persist data, such as job descriptions, project names, or metadata fields. Examine any HTML source of rendered pages using browser developer tools to detect injected script tags or encoded payloads in stored values.
    Affected if User-supplied input fields in the Web UI accept and render content without proper output encoding

A user is affected if IBM InfoSphere Information Server version 11.7 is installed with the Web UI component enabled and accessible, as this specific version contains the stored XSS vulnerability in the Web UI.

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; implement output encoding and input validation for all user-supplied data in the Web UI; consider implementing Content Security Policy headers to mitigate XSS execution.

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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