dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2024-28798

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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

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 vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code into the Web interface, which persists and executes when other users access the affected functionality. This can enable credential theft or session hijacking within trusted sessions.

MitigationApply the IBM patch for CVE-2024-28798. Until then, implement output encoding and input validation on all user-supplied data rendered in the Web UI, and consider deploying Web Application Firewall rules to detect XSS attack patterns.

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
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 checks

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

  1. Confirm IBM InfoSphere Information Server version
    Locate the installation directory and check the version file, or use the IBM installation manager or version command-line tool to query the installed version. Common paths include /opt/IBM/InformationServer or C:\IBM\InformationServer on Windows.
    Affected if The installed version is exactly 11.7.0 (no patches applied)
  2. Verify Web UI component is accessible
    Access the Web UI login page by navigating to the InfoSphere web console URL (typically https://hostname:9443/ibm/console or similar port). Confirm the service is running by checking the WebSphere or HTTP Server status.
    Affected if The Web UI is reachable and users authenticate to it
  3. Inspect stored content in Web UI input fields
    Log into the Web UI as a standard user. Navigate to input forms (metadata definitions, job parameters, repository descriptions). View page source or use browser developer tools to examine if user-supplied values are rendered with proper encoding.
    Affected if User-supplied data in Web UI fields renders unescaped HTML or JavaScript (visible as <script> tags in page source)
  4. Review Web server access logs for XSS patterns
    Examine HTTP server logs (typically in IBM/HTTPServer/logs or WebSphere logs directory) for request parameters containing script tags, javascript: URIs, or event handlers like onerror, onload.
    Affected if Logs contain requests with XSS payloads in parameters that get stored and reflected back

You are affected if IBM InfoSphere Information Server version 11.7 is installed with the Web UI accessible and no patches applied, particularly if stored XSS payloads appear in web logs or unencoded user content renders in the interface.

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 the IBM patch for CVE-2024-28798. Until then, implement output encoding and input validation on all user-supplied data rendered in the Web UI, and consider deploying Web Application Firewall rules to detect XSS attack patterns.

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-28798 — 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-28798 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