dbcve.org
Infosphere Information Governance CatalogApplication · Ibm

CVE-2018-1875

MEDIUM · 6.1 CVSS v3.0 Published 2019-03-05
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 Governance Catalog 11.3, 11.5, and 11.7 could allow a remote attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially-crafted Web site, a remote attacker could exploit this vulnerability to spoof the URL displayed to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim. IBM X-Force ID: 151639.

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 Governance Catalog versions 11.3, 11.5, and 11.7 contains an open redirect vulnerability. By crafting a malicious URL that includes a specially-crafted redirect parameter, an attacker can cause the application to redirect users to an arbitrary external website while making it appear the URL originates from the trusted IBM domain. This enables phishing attacks where victims believe they are visiting a legitimate IBM site.

MitigationApply IBM security patches for this vulnerability. Additionally, implement strict URL validation that only allows redirects to pre-approved, internal domains or use relative path redirects instead of user-supplied absolute URLs.

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 Governance CatalogApplication
Affected:= 11.3= 11.5= 11.7
Infosphere Information Server On CloudApplication
Affected:= 11.5= 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.0/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. Identify the installed version of IBM InfoSphere Information Governance Catalog
    Check the product version through the IBM InfoSphere administration console, installation directory, or version lookup command for your deployment method. Compare against the affected versions: 11.3, 11.5, and 11.7.
    Affected if The installed version is exactly 11.3, 11.5, or 11.7 for the on-premises Information Governance Catalog.
  2. Identify the installed version of IBM InfoSphere Information Server On Cloud
    Check the cloud service version through the IBM Cloud dashboard or administrative interface for your Information Server On Cloud instance. Compare against the affected versions: 11.5 and 11.7.
    Affected if The installed version is exactly 11.5 or 11.7 for Information Server On Cloud.
  3. Locate redirect functionality in the application
    Search application configuration files and web server settings for redirect or URL redirection modules. Inspect the application's URL handling code for parameters that control navigation or redirection behavior.
    Affected if The application contains redirect functionality that accepts user-supplied or parameter-driven URL targets.
  4. Test for open redirect vulnerability
    Craft a test URL with a redirect parameter pointing to an external domain (for example, appending a redirect parameter with a value of https://example.com to a known IBM InfoSphere URL). Observe whether the application redirects to the external domain without validation.
    Affected if The application redirects to an arbitrary external URL supplied in the redirect parameter without proper validation or restriction.

Your environment is affected if you are running IBM InfoSphere Information Governance Catalog version 11.3, 11.5, or 11.7 or IBM InfoSphere Information Server On Cloud version 11.5 or 11.7, and the application contains redirect functionality that can be manipulated to redirect users to external domains.

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 security patches for this vulnerability. Additionally, implement strict URL validation that only allows redirects to pre-approved, internal domains or use relative path redirects instead of user-supplied absolute URLs.

Fix this in Infosphere Information Governance Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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