dbcve.org
Emptoris Spend AnalysisApplication · Ibm

CVE-2017-1446

MEDIUM · 5.4 CVSS v3.1 Published 2017-08-30
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 Spend Analysis 9.5.0.0 through 10.1.1 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: 128171.

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 Spend Analysis versions 9.5.0.0 through 10.1.1 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code through user input fields, which then executes in the browsers of other users viewing the affected content, potentially leading to session hijacking and credentials disclosure.

MitigationApply vendor-supplied patches for this vulnerability. Implement output encoding and input validation for all user-supplied data in the Web UI. Consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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 Spend AnalysisApplication
Affected:= 9.5.0.0= 9.5.0.1= 9.5.0.2= 9.5.0.3= 9.5.0.4= 10.0.0.0= 10.0.0.1= 10.0.1.0= 10.0.2.0= 10.0.4.0= 10.1.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.1/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. Identify installed IBM Emptoris Spend Analysis version
    Locate the product version through the application admin interface, about page, or installation metadata files. Common locations include the application's help/about section or version configuration files in the installation directory.
    Affected if The installed version matches any of the affected versions: 9.5.0.0, 9.5.0.1, 9.5.0.2, 9.5.0.3, 9.5.0.4, 10.0.0.0, 10.0.0.1, 10.0.1.0, 10.0.2.0, 10.0.4.0, or 10.1.1.0.
  2. Confirm Web UI is enabled and accessible
    Verify that the IBM Emptoris Spend Analysis web interface is deployed and reachable. Check if the application is serving HTTP/HTTPS requests on its configured port.
    Affected if The Web UI is active and accessible to users or attackers.
  3. Review user input fields in the Web UI
    Examine the web interface for input fields that accept user data, such as text boxes, forms, or data import fields. Identify which fields accept and store user-supplied content that gets rendered back to users.
    Affected if User input fields exist that accept and store data without proper sanitization or output encoding.
  4. Search for stored malicious scripts in application data
    Inspect the application's database or stored data for any unexpected script tags, JavaScript code, or HTML elements that may have been injected into user-controlled fields. Use database queries or application audit logs to identify suspicious stored content.
    Affected if Stored XSS payloads containing script tags or JavaScript code are found in any user input fields or data storage.

You are affected if the installed version matches one of the listed affected versions AND the Web UI is accessible AND user input fields accept unsanitized content that could execute in other users' browsers.

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 vendor-supplied patches for this vulnerability. Implement output encoding and input validation for all user-supplied data in the Web UI. Consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Emptoris Spend Analysis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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