CVE-2017-1450
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 · uneditedIBM 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: 128177.
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 confidenceIBM Emptoris Sourcing versions 9.5 through 10.1.3 contains an open redirect vulnerability. By crafting a malicious URL, an attacker can trick users into visiting a trusted-looking URL that actually redirects to a malicious site, enabling phishing attacks and credential theft.
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= 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.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Emptoris Sourcing versionLocate the installed version through the application admin interface (typically under Help > About or System > Version), check deployment configuration files, or query the application's system information endpoint if availableAffected if The installed version matches any of: 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
-
Confirm web interface is accessibleVerify that the IBM Emptoris Sourcing web application is exposed and reachable over HTTP/HTTPS. Check network configuration to determine if the application is accessible internally or externallyAffected if The web interface is accessible and the version falls within the affected range listed above
-
Review redirect URL handlingExamine application logs or use a web proxy to observe how the application handles redirect parameters in URLs. Look for parameters that control redirection destinations (commonly 'redirect', 'url', 'target', or 'dest' parameters)Affected if The application accepts user-controlled parameters that influence redirect destinations and the version is in the affected range
If IBM Emptoris Sourcing is deployed with a version between 9.5 and 10.1.0 inclusive and its web interface is accessible, the environment is likely affected by this open redirect vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate IBM Emptoris Sourcing to a version beyond 10.1.3 that addresses this vulnerability, or implement strict URL validation and redirect whitelisting to ensure only trusted destinations are allowed.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2017-1450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1450 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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