CVE-2016-8947
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.x through 10.1.x 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: 118834
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 confidenceIBM Emptoris Sourcing versions 9.5.x through 10.1.x contain an open redirect vulnerability where the application fails to properly validate redirect URLs. An attacker can craft malicious URLs that appear to originate from the trusted Emptoris domain but actually redirect users to arbitrary external websites. This enables phishing attacks where victims see a trusted URL in their browser while being redirected to malicious sites.
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.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= 10.1.1CVSS 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 by checking the application about page, version info in the administration console, or the software inventory documentation. Common locations include the login page footer, help/about section, or system information within the application.Affected if The installed version matches any of: 9.5, 9.5.0.1, 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, or 10.1.1
-
Confirm web interface is accessibleVerify that the Emptoris Sourcing web interface is reachable and operational. Open a browser session to the application's base URL and confirm normal authentication and navigation functions work.Affected if The web interface is accessible and the application is in production use, as the open redirect vulnerability is exploitable through HTTP requests to the web application.
-
Inspect redirect parameters in application trafficUse browser developer tools or a proxy to capture HTTP requests. Look for URL parameters that handle redirection such as 'redirect', 'url', 'target', 'dest', or 'next'. Examine whether these parameters accept full URLs or relative paths.Affected if The application uses redirect parameters that accept arbitrary URLs without validation, enabling the open redirect vulnerability to be triggered.
-
Review application logs for external redirect patternsExamine application server logs for requests containing external domains in redirect-related parameters. Search for patterns where redirect parameters contain 'http://' or 'https://' pointing to domains outside the organization's control.Affected if Logs show redirect parameters being used with external URLs, indicating the vulnerable code path is being exercised.
You are affected if your installed IBM Emptoris Sourcing version is 9.5.x or 10.0.x or 10.1.x and the web application is accessible with redirect functionality in use.
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 dataImplement strict URL validation for all redirect parameters, using an allow-list approach to only permit known-safe destinations within the application or on approved domains. Additionally, display a warning page before redirecting to external sites to make redirects transparent to users.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8947 — 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-2016-8947 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