dbcve.org
Websphere CommerceApplication · Ibm

CVE-2017-1398

MEDIUM · 6.1 CVSS v3.0 Published 2017-07-10
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 WebSphere Commerce Enterprise, Professional, Express, and Developer 6.0, 7.0, and 8.0 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: 127385.

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 WebSphere Commerce versions 6.0, 7.0, and 8.0 contain an open redirect vulnerability where the application does not properly validate redirect URLs. An attacker can craft a malicious URL that appears to be on a trusted IBM domain but actually redirects victims to an attacker-controlled website, enabling phishing attacks and potential credential theft.

MitigationImplement strict validation of redirect parameters to ensure they point to trusted domains only, or use an allowlist approach for permitted redirect destinations. Consider displaying a warning page before redirecting to external sites.

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
Websphere CommerceApplication
Affected:= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.0.6= 8.0.0.7= 8.0.0.8= 8.0.0.9= 8.0.0.10= 8.0.0.11

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 if IBM WebSphere Commerce is installed
    Check your system for IBM WebSphere Commerce components, typically installed in WebSphere application server profiles. Look for commerce-related directories or check running processes for WebSphere Commerce instances.
    Affected if IBM WebSphere Commerce software is found on the system
  2. Determine the installed WebSphere Commerce version
    Locate the version file or check the WebSphere Commerce administration console for the exact version number. The version is typically displayed in the Commerce administration interface or in installation logs.
    Affected if The installed version matches 8.0.0.0 through 8.0.0.11
  3. Identify exposed web endpoints that handle redirects
    Review your WebSphere Commerce web application for URLs containing redirect or forward parameters (such as 'redirect', 'url', 'forward', or similar query parameters). Check public-facing storefront or admin URLs.
    Affected if Redirect-handling parameters are present in accessible web URLs
  4. Test redirect parameter behavior
    Submit a crafted request with an external domain as the redirect parameter value (for example, add '?redirect=http://attacker.example.com' to a known WebSphere Commerce URL) and observe if the application issues a redirect to the external domain.
    Affected if The application redirects to an arbitrary external domain without validation

You are affected if IBM WebSphere Commerce version 8.0.0.0 through 8.0.0.11 is running and the redirect parameter functionality is accessible and allows unvalidated external domains as redirect targets.

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

Implement strict validation of redirect parameters to ensure they point to trusted domains only, or use an allowlist approach for permitted redirect destinations. Consider displaying a warning page before redirecting to external sites.

Fix this in Websphere Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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