CVE-2011-1355
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 WebSphere Application Server (WAS) 6.1 before 6.1.0.39 and 7.0 before 7.0.0.19 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via the logoutExitPage parameter.
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 WebSphere Application Server's logout functionality. The logoutExitPage parameter is not properly validated, allowing attackers to supply an arbitrary URL that users are redirected to after logout, 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= 6.1= 6.1.0= 6.1.0.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.5= 6.1.0.7= 6.1.0.9= 6.1.0.11= 6.1.0.12= 6.1.0.15CVSS 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/I:P/A:P
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.
-
Determine the installed WebSphere Application Server versionRun the versionInfo command from the bin directory (versionInfo.bat on Windows, versionInfo.sh on Linux/UNIX) or check the About WebSphere Application Server console pageAffected if The version listed is 6.1.0.0 through 6.1.0.15 (or any 6.1.x variant listed in the affected versions)
-
Identify if logout functionality uses the logoutExitPage parameterExamine the logout form or servlet configuration in the web.xml deployment descriptor and look for any logout mechanism that accepts a logoutExitPage parameterAffected if A logout feature exists that accepts a logoutExitPage or similar redirect parameter
-
Test redirect behavior on the logout endpointAccess the logout URL with a test parameter such as logoutExitPage=http://example.com and observe if the application redirects to the supplied URL after logoutAffected if The application redirects to an arbitrary external URL supplied in the logoutExitPage parameter without validation
-
Check for input validation on redirect parametersReview the web.xml or custom logout servlet code for validation logic that whitelist-validates the logoutExitPage parameter before useAffected if No whitelist validation exists and arbitrary URLs can be passed through the logoutExitPage parameter
You are affected if your WebSphere version is 6.1.0.0 through 6.1.0.15 and your logout functionality accepts and acts upon an unvalidated logoutExitPage parameter, causing redirection to attacker-controlled URLs.
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 dataUpgrade IBM WebSphere Application Server to version 6.1.0.39 or later, or 7.0.0.19 or later. Alternatively, implement strict input validation on the logoutExitPage parameter to whitelist only trusted redirect URLs.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1355 — 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-2011-1355 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