dbcve.org
Infosphere Information ServerApplication · Ibm

CVE-2022-35715

HIGH · 7.5 CVSS v3.1 Published 2022-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in a stack trace. This information could be used in further attacks against the system. IBM X-Force ID: 231202.

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 returns detailed technical error messages including stack traces to users, exposing sensitive system information such as file paths, library versions, code structure, and potentially database credentials. This information disclosure (CWE-209) can aid attackers in planning further exploitation.

MitigationConfigure custom error pages to display generic user-friendly messages while logging detailed stack traces server-side only. Disable detailed error reporting in production environments.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 and inspect the product installation directory, typically under /opt/IBM/InformationServer or C:\IBM\InformationServer. Check for version.txt or use the 'version.sh' / 'version.bat' utility in the installation bin folder.
    Affected if The installed version is exactly 11.7 (the only affected version listed)
  2. Check error handling configuration
    Locate the WebSphere Application Server configuration files that govern error reporting. In the WebSphere admin console or configuration files (web.xml, ibm-web-ext.xml), look for the 'isErrorPage' attribute and 'error-code' mappings in the deployment descriptor.
    Affected if Error pages are configured to display detailed stack traces or the 'isErrorPage' attribute is set to 'true' for generic error handlers
  3. Verify custom error page configuration
    Examine the application's web.xml deployment descriptor (found in the war/ear file or installation directory under the web module) for <error-page> mappings. Also check the IBM-specific configuration files (such as the InformationServer config or WebSphere plugin-cfg.xml) for custom error handler definitions.
    Affected if No <error-page> entries are defined, or the configured error pages contain error code, exception type, or location mappings that display technical details
  4. Inspect WebSphere error report settings
    In the WebSphere Application Server admin console (typically at port 9060), navigate to Application servers > server1 > Web container > Error handling, or inspect the ibm-web-bnd.xmi/ibm-web-bnd.xml files for the property 'enableErrorDetails' or similar.
    Affected if The 'enableErrorDetails' property is set to true, or detailed error reporting is not disabled in the production environment settings

A user is affected if IBM InfoSphere Information Server version 11.7 is installed AND detailed error reporting is enabled without custom error pages configured to suppress stack traces.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure custom error pages to display generic user-friendly messages while logging detailed stack traces server-side only. Disable detailed error reporting in production environments.

Recommended fix Moderate confidence

Apply IBM InfoSphere Information Server 11.7 security patch (IFix) for CVE-2022-35715

  1. 1. Visit IBM Fix Central (https://www.ibm.com/support/fixcentral/) to search for security fixes
  2. 2. Select 'IBM InfoSphere Information Server' as the product and version 11.7
  3. 3. Search for CVE-2022-35715 or APAR reference to locate the applicable security patch
  4. 4. Download and apply the recommended security patch following IBM's installation instructions
  5. 5. Verify the patch was applied successfully and test that detailed error messages are no longer exposed
Caveat Review IBM patch documentation for any required configuration changes or prerequisites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infosphere Information Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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