CVE-2016-3047
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 · uneditedOpen redirect vulnerability in IBM FileNet Workplace 4.0.2 through 4.0.2.14 IF001 allows remote authenticated users to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.
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 confidenceOpen redirect vulnerability in IBM FileNet Workplace versions 4.0.2 through 4.0.2.14 IF001 allows authenticated users to craft URLs that redirect users to arbitrary external websites, enabling phishing 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= 4.0.2CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/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 if IBM FileNet Workplace is installedLocate the installation directory or check system inventory for IBM FileNet Workplace componentsAffected if The product is present on the system
-
Determine the installed version of IBM FileNet WorkplaceCheck the version information in the application metadata, About section, or installation logs. Compare the version number against the affected range: 4.0.2 through 4.0.2.14 IF001Affected if The installed version falls within 4.0.2 through 4.0.2.14 IF001
-
Verify if authentication-based features are accessibleConfirm that user authentication to the Workplace application is functional and that authenticated users can access the application interfaceAffected if Users can authenticate and access the application after version confirmation
-
Check for exposed redirect parametersInspect application URLs for redirect or navigation parameters (such as 'redirect=', 'target=', or similar) that accept URL valuesAffected if The application accepts redirect parameters in URLs accessible to authenticated users
-
Test for external redirect capabilityAs an authenticated user, attempt to access a crafted URL containing an external domain in the redirect parameter to observe if the application allows redirection to arbitrary sitesAffected if The application permits redirection to external domains rather than restricting to whitelisted internal destinations
The environment is affected if IBM FileNet Workplace version 4.0.2 through 4.0.2.14 IF001 is installed and the application allows redirect parameters to point to external domains.
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 validation of redirect parameters to allow only whitelisted internal destinations; apply URL canonicalization and reject any redirect URLs containing external domains or suspicious patterns.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3047 — 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-3047 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