Jboss PortalApplication · Redhat
CVE-2014-0245
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 · uneditedIt was found that the implementation of the GTNSubjectCreatingInterceptor class in gatein-wsrp was not thread safe. For a specific WSRP endpoint, under high-concurrency scenarios or scenarios where SOAP messages take long to execute, it was possible for an unauthenticated remote attacker to gain privileged information if WS-Security is enabled for the WSRP Consumer, and the endpoint in question is being used by a privileged user. This affects JBoss Portal 6.2.0.
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 · moderate confidenceThe GTNSubjectCreatingInterceptor class in gatein-wsrp contains a race condition where authentication context from privileged users can leak to concurrent requests from unauthenticated attackers under high-load or long-running SOAP scenarios when WS-Security is enabled for the WSRP Consumer.
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 PortalApplication
= 6.2.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 JBoss Portal installation and versionLocate the JBoss Portal installation directory and check the version. This is typically found in the product documentation or via the portal's admin interface version information.Affected if The installed version is exactly Red Hat JBoss Portal 6.2.0.
-
Verify WSRP Consumer is configuredCheck if the WSRP Consumer endpoint is configured in the JBoss Portal installation. Look for WSRP-related configuration files or admin settings that define a WSRP Consumer service.Affected if A WSRP Consumer endpoint is configured and active.
-
Confirm WS-Security is enabled for WSRPInspect the WSRP Consumer configuration for WS-Security settings. This is typically found in the WSRP configuration files or the web services security configuration within the JBoss Portal admin console.Affected if WS-Security is explicitly enabled for the WSRP Consumer endpoint.
-
Check for GTNSubjectCreatingInterceptor presenceLocate and examine the gatein-wsrp components in the deployment, specifically looking for the GTNSubjectCreatingInterceptor class and its configuration in the WSRP handler chain.Affected if The GTNSubjectCreatingInterceptor is present in the WSRP handler chain.
A user is affected if they are running JBoss Portal 6.2.0 with WSRP Consumer configured and WS-Security enabled, as this enables the race condition in GTNSubjectCreatingInterceptor.
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 dataEnsure the GTNSubjectCreatingInterceptor is made thread-safe (typically by removing shared mutable state or adding proper synchronization), or disable WS-Security for the affected WSRP Consumer endpoint until a patched version is available.
Fix this in Jboss Portal
Scoped from the published advisory
- 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-2014-0245 — 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-2014-0245 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