dbcve.org
Emptoris SourcingApplication · Ibm

CVE-2017-1447

MEDIUM · 5.4 CVSS v3.0 Published 2017-08-31
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 Emptoris Sourcing 9.5 - 10.1.3 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: 128172.

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 Emptoris Sourcing versions 9.5 through 10.1.3 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user can embed arbitrary JavaScript code into the web interface, which executes in the browsers of other users viewing the affected content, potentially allowing credential theft or session hijacking within trusted sessions.

MitigationApply IBM's security patches for this vulnerability. Additionally, implement robust input validation and output encoding for all user-supplied data in the web UI to prevent XSS attacks.

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
Emptoris SourcingApplication
Affected:= 9.5= 9.5.0.1= 9.5.0.2= 9.5.1.0= 9.5.1.1= 9.5.1.2= 9.5.1.3= 10.0.0= 10.0.1= 10.0.2= 10.0.4= 10.1.0

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.0/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 Emptoris Sourcing is installed
    Identify the installed application by checking the product name in the web interface header, login page, or application documentation. Look for 'Emptoris Sourcing' branding.
    Affected if The application is not IBM Emptoris Sourcing.
  2. Determine the installed version
    Locate the version number in the product UI (typically in Help > About or in the footer of pages), in installation logs, or in the deployment configuration files.
    Affected if The version falls within 9.5 through 10.1.3 inclusive, including these specific versions: 9.5, 9.5.0.1, 9.5.0.2, 9.5.1.0, 9.5.1.1, 9.5.1.2, 9.5.1.3, 10.0.0, 10.0.1, 10.0.2, 10.0.4, 10.1.0.
  3. Verify the web interface is enabled
    Confirm the Emptoris Sourcing web application is accessible by attempting to reach the application URL through a browser or checking the application server configuration.
    Affected if The web interface is not exposed or not accessible.
  4. Confirm user authentication is required
    Verify that the application requires login. Attempt to access the application without credentials and confirm redirect to a login page.
    Affected if The application allows unauthenticated access to content entry points.
  5. Inspect for stored XSS payloads in application data
    Review database tables or application logs for suspicious script tags, JavaScript event handlers, or encoded XSS patterns in user-generated fields such as supplier names, item descriptions, or document metadata.
    Affected if Malicious script content is found stored in the application database.

You are affected if IBM Emptoris Sourcing is running and the installed version is between 9.5 and 10.1.3 inclusive, the web interface is accessible, and user authentication is required for access.

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 patches for this vulnerability. Additionally, implement robust input validation and output encoding for all user-supplied data in the web UI to prevent XSS attacks.

Fix this in Emptoris Sourcing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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