dbcve.org
Websphere CommerceApplication · Ibm

CVE-2017-1569

HIGH · 7.5 CVSS v3.0 Published 2017-10-03
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 WebSphere Commerce 7.0 and 8.0 contains an unspecified vulnerability in Marketing ESpot's that could cause a denial of service. IBM X-Force ID: 131779.

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 WebSphere Commerce versions 7.0 and 8.0 contain a denial of service vulnerability in the Marketing ESpot component. The specific vulnerability details are not disclosed, but exploitation could cause service disruption. The flaw has a CVSS score of 7.5 (HIGH), indicating significant potential impact on availability.

MitigationApply the relevant IBM WebSphere Commerce patches or upgrades to versions 7.0.0.x and 8.0.0.x as specified in IBM's security advisory for CVE-2017-1569. If patches are unavailable, implement network-level rate limiting and monitoring for the ESpot endpoints as a compensating control.

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:= 7.0.0.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 8.0.0.0= 8.0.0.1= 8.0.0.2

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 IBM WebSphere Commerce installation
    Locate the WebSphere Commerce installation directory. Common paths include /opt/ibm/WebSphere/Commerce or C:\IBM\WebSphere\Commerce on Windows. Check for the presence of Commerce directory structure and bin folders.
    Affected if IBM WebSphere Commerce software is not found on the system, the system is not affected by this CVE.
  2. Determine installed WebSphere Commerce version
    Check the version file in the Commerce installation directory, typically found in the root of the Commerce installation folder or in a versioninfo.properties file. Alternatively, run: java -jar <installer_path>/versionInfo.jar or check the WC_version file in the installation directory.
    Affected if The installed version matches exactly 7.0.0.0 through 7.0.0.8 or 8.0.0.0 through 8.0.0.2 - these specific versions are affected by CVE-2017-1569.
  3. Verify Marketing ESpot component is configured
    Check if the Marketing (ESpot) module is enabled. Inspect the WC_eardir/xml/config directory for marketing-related XML configuration files such as MarketingOverride.xml or ESpot configuration files. Look for entries that enable or configure ESpot marketing activities.
    Affected if The Marketing ESpot component is actively configured and in use - the vulnerability exists in this component specifically.
  4. Review ESpot endpoint exposure
    Identify if ESpot marketing endpoints are exposed to the network. Check the web.xml deployment descriptor in the Stores or Catalog ear for servlet mappings related to ESpot (typically under /webapp/servlet/ESpot or similar). Determine if these endpoints are accessible from external networks.
    Affected if ESpot endpoints are externally accessible without proper network segmentation or filtering, increasing exploitation risk.

A system is affected if IBM WebSphere Commerce versions 7.0.0.0-7.0.0.8 or 8.0.0.0-8.0.0.2 is installed AND the Marketing ESpot component is configured and exposed.

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 relevant IBM WebSphere Commerce patches or upgrades to versions 7.0.0.x and 8.0.0.x as specified in IBM's security advisory for CVE-2017-1569. If patches are unavailable, implement network-level rate limiting and monitoring for the ESpot endpoints as a compensating control.

Fix this in Websphere Commerce 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-2017-1569 — 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-1569 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