dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2022-22443

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-28
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: 224440.

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 executes within authenticated users' sessions, potentially allowing credential theft or session hijacking through a trusted session.

MitigationApply IBM's security patch for CVE-2022-22443 from Fix Central. Until patched, implement output encoding and input validation on all web UI fields as compensating controls.

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 product installation directory and check the version. On Windows, look in C:\IBM\InformationServer\. On Linux/Unix, check /opt/IBM/InformationServer/. Use the versionInfo command or check version.xml in the installation directory.
    Affected if The installed version is IBM InfoSphere Information Server 11.7 exactly (or an affected 11.7.x release)
  2. Verify the web UI component is accessible
    Check if the web-based UI is enabled and accessible. Access the administration console URL (typically https://hostname:9443/ibm/console or similar) and verify the login page loads.
    Affected if The web UI is exposed and accessible to users
  3. Identify web UI entry points that accept user input
    Review the web UI for form fields, search boxes, or data entry screens where user-supplied content can be stored and displayed back to other users (such as job names, descriptions, or metadata fields).
    Affected if User-editable fields exist in the web interface that can store and display content back to authenticated users
  4. Inspect stored content for suspicious script tags
    Examine any stored data in the web UI database or configuration files for unexpected HTML script tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.) in user-defined fields.
    Affected if Stored data contains unsanitized script tags or JavaScript event handlers that could execute in other users' sessions
  5. Review web access logs for XSS probe attempts
    Check HTTP server access logs (typically in the logs directory of the web application server) for requests containing script tags, <img src=x onerror=>, or similar patterns in query parameters or POST body fields.
    Affected if Logs show injection attempts with XSS payloads targeting web UI endpoints

You are affected if IBM InfoSphere Information Server version 11.7 is installed and its web UI is accessible, as the stored XSS vulnerability exists in that specific version's web 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 IBM's security patch for CVE-2022-22443 from Fix Central. Until patched, implement output encoding and input validation on all web UI fields as compensating controls.

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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