dbcve.org
Jboss Enterprise Portal PlatformApplication · Redhat

CVE-2011-2941

MEDIUM · 5.8 CVSS v2.0 Published 2014-02-26
Fix available
A fix is available. Upgrade to after 5.1.1 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Open redirect vulnerability in Red Hat JBoss Enterprise Portal Platform before 5.2.0 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the initialURI 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 confidence

Open redirect vulnerability in Red Hat JBoss Enterprise Portal Platform versions prior to 5.2.0 allows remote attackers to redirect users to arbitrary external websites via a crafted URL containing a malicious value in the initialURI parameter. This enables phishing attacks where users are tricked into visiting malicious sites while believing they are navigating within the legitimate portal.

MitigationUpgrade to JBoss Enterprise Portal Platform 5.2.0 or later. If upgrading is not feasible, implement strict validation of the initialURI parameter to ensure redirects only point to internal, relative paths or a whitelist of allowed domains.

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
Jboss Enterprise Portal PlatformApplication
Affected:<= 5.1.1= 4.3.0= 5.0.0= 5.0.1= 5.1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify JBoss Enterprise Portal Platform installation
    Check for JBoss Enterprise Portal Platform by looking for jboss-portal, jboss-epp, or portal-related directories in common installation paths such as /opt/jboss, /usr/share/jboss, or C:\Program Files\JBoss. Also check for running processes containing 'jboss' or 'portal' in their command line.
    Affected if The product is installed on the system
  2. Determine installed version
    Locate version information in the portal installation. Common locations include: version.properties, about.xml, or the JBoss admin console. The version can also be identified via the portal's 'About' page if accessible.
    Affected if The installed version is 5.1.1 or earlier, or specifically 4.3.0, 5.0.0, 5.0.1, or 5.1.0
  3. Verify portal web interface is accessible
    Confirm the portal HTTP/HTTPS endpoints are active and reachable. The vulnerability requires the web interface to be accessible for the redirect to be exploitable.
    Affected if The portal web interface is exposed and accessible to users or attackers
  4. Check for initialURI parameter usage
    Review application logs or network traffic for requests containing the 'initialURI' parameter. This parameter is used by the portal for redirect functionality after authentication or other operations.
    Affected if Requests with initialURI parameter are being processed by the portal
  5. Test for open redirect vulnerability
    If authorized, send a crafted request with an external URL in the initialURI parameter (for example: initialURI=http://malicious-site.com). Check if the portal redirects to the external site without validation.
    Affected if The portal redirects to arbitrary external URLs provided in the initialURI parameter without validating they are internal paths

A user is affected if JBoss Enterprise Portal Platform version 5.1.1 or earlier (including 4.3.0, 5.0.0, 5.0.1, 5.1.0) is installed and the portal web interface handles the initialURI parameter without validating it points to internal paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.1.1
Interim mitigation

Upgrade to JBoss Enterprise Portal Platform 5.2.0 or later. If upgrading is not feasible, implement strict validation of the initialURI parameter to ensure redirects only point to internal, relative paths or a whitelist of allowed domains.

Fix this in Jboss Enterprise Portal Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-2941 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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