dbcve.org
Emptoris SourcingApplication · Ibm

CVE-2017-1449

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 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: 128174.

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

Open redirect vulnerability in IBM Emptoris Sourcing versions 9.5 through 10.1.3 allows remote attackers to craft malicious URLs that appear to originate from the trusted application but redirect users to attacker-controlled websites for phishing attacks and credential theft.

MitigationImplement strict allowlist-based URL validation for all redirect endpoints and display interstitial warning pages before redirecting to external domains.

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. Identify installed IBM Emptoris Sourcing version
    Access the application administration interface or check the product documentation for the installed version. Look in the 'About' section, system information page, or version details within the web application. If you have server access, check installation directories for version files or the manifest.
    Affected if The installed version matches any of the following: 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, or 10.1.0.
  2. Locate redirect endpoints in the application
    Review application URLs and parameter handling for patterns that perform redirects, such as 'redirect', 'url', 'next', 'dest', or 'target' parameters. Check the web server logs or application configuration for redirect-related servlet mappings or endpoint definitions.
    Affected if The application contains any URL redirect or forwarding functionality that accepts user-supplied input.
  3. Test for open redirect vulnerability
    Using a browser or HTTP tool, craft a test URL that includes the application URL followed by a redirect parameter pointing to an external domain you control (for example: https://your-emptoris-server/someendpoint?redirect=http://example.com). Observe whether the application redirects the browser to the external domain without validation.
    Affected if The application redirects to the external URL supplied in the parameter without validating the target domain or displaying any warning interstitial page.
  4. Review redirect URL validation configuration
    Examine the application configuration files, web.xml, or any custom URL validation settings for how redirects are handled. Look for allowlist or blocklist configurations that control which domains are permitted in redirects.
    Affected if No allowlist-based validation is configured for redirect endpoints, or the validation can be bypassed.

You are affected if your installed IBM Emptoris Sourcing version is 9.5 through 10.1.0 and the application performs unvalidated redirects 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

Implement strict allowlist-based URL validation for all redirect endpoints and display interstitial warning pages before redirecting to external domains.

Fix this in Emptoris Sourcing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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