CVE-2010-3473
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 the Workplace (aka WP) component in IBM FileNet P8 Application Engine (P8AE) 3.5.1 before 3.5.1-021 allows remote attackers 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 P8 Application Engine Workplace component allows attackers to craft malicious URLs that redirect users to arbitrary external websites for phishing attacks. Affects versions 3.5.1 before 3.5.1-021.
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= 3.5.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 the IBM FileNet P8 Application Engine versionCheck the installed version of IBM FileNet P8 Application Engine via the administration console, installation logs, or version.properties file typically located in the Application Engine installation directoryAffected if The installed version is 3.5.1 and the patch level is before 3.5.1-021
-
Verify the Workplace component is deployedCheck if the Workplace web application is deployed and accessible on the Application Engine server. This can be done via the WebSphere or WAS administration console by listing deployed applications or by accessing the Workplace URL endpointAffected if The Workplace component is deployed and accessible
-
Confirm the exact patch level of version 3.5.1Examine the build number or patch information for the installation. This may be visible in the Workplace login page footer, the IBM Enterprise Manager, or via the CE_Operations (Content Engine) MBean queries if availableAffected if The patch level shows a build earlier than 3.5.1-021, indicating the vulnerability is present
-
Review URL handling in the Workplace applicationTest the redirect behavior by observing URL parameters when logging into Workplace. An open redirect vulnerability would allow a parameter such as 'returnUrl' or similar to redirect to an external domain without validationAffected if The application allows arbitrary external URLs in redirect parameters without proper validation
The environment is affected if IBM FileNet P8 Application Engine version 3.5.1 with the Workplace component is deployed and the patch level is before 3.5.1-021.
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 dataApply vendor patch 3.5.1-021 or later to the IBM FileNet P8 Application Engine Workplace component to remediate the open redirect vulnerability.
- 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-2010-3473 — 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-2010-3473 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