Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1160574 - (CVE-2014-7827) CVE-2014-7827 JBoss Security: Wrong security context loaded when using SAML2 STS Login Module
CVE-2014-7827 JBoss Security: Wrong security context loaded when using SAML2 ...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20150211,reported=2...
: Security
Depends On: 1162884 1162885 1163831 1163832 1163833 1163835 1163836 1163837 1163838 1163839 1163841 1163842 1163844
Blocks: 1155350 1160563 1210482
  Show dependency tree / graph
 
Reported: 2014-11-05 03:13 EST by Arun Babu Neelicattu
Modified: 2015-11-02 12:58 EST (History)
30 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that when processing undefined security domains, the org.jboss.security.plugins.mapping.JBossMappingManager implementation would fall back to the default security domain if it was available. A user with valid credentials in the defined default domain, with a role that is valid in the expected application domain, could perform actions that were otherwise not available to them. When using the SAML2 STS Login Module, JBossMappingManager exposed this issue due to the PicketLink Trust SecurityActions implementation using a hardcoded default value when defining the context.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-02 12:58:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0215 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform 6.3.3 update 2015-02-11 20:06:34 EST
Red Hat Product Errata RHSA-2015:0216 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform 6.3.3 update 2015-02-11 20:18:36 EST
Red Hat Product Errata RHSA-2015:0217 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform 6.3.3 update 2015-02-11 20:16:58 EST
Red Hat Product Errata RHSA-2015:0218 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform 6.3.3 update 2015-02-11 20:36:41 EST
Red Hat Product Errata RHSA-2015:0850 normal SHIPPED_LIVE Important: Red Hat JBoss BRMS 6.1.0 update 2015-04-16 16:02:45 EDT
Red Hat Product Errata RHSA-2015:0851 normal SHIPPED_LIVE Important: Red Hat JBoss BPM Suite 6.1.0 update 2015-04-16 16:02:37 EDT

  None (edit)
Description Arun Babu Neelicattu 2014-11-05 03:13:34 EST 
It was discovered that when dealing with undefined security domains, the org.jboss.security.plugins.mapping.JBossMappingManager implementation would fall back to the default security domain if available. A user with valid credentials in the defined default domain, with a role that is valid in the expected application domain, can perform actions that was otherwise not available to them. When using the SAML2 STS Login Module, JBossMappingManager exposes this issue since PicketLink Trust SecurityActions implementation use a hardcoded default value when defining the context.
Comment 1 Arun Babu Neelicattu 2014-11-05 03:17:11 EST 
Acknowledgements:

This issue was discovered by Ondra Lukas of the Red Hat Quality Engineering Team.
Comment 2 Arun Babu Neelicattu 2014-11-05 03:23:39 EST 
Statement:

Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/
Comment 5 errata-xmlrpc 2015-02-11 15:06:42 EST 
This issue has been addressed in the following products:

  JBoss Enterprise Application Platform 6.3.3

Via RHSA-2015:0215 https://rhn.redhat.com/errata/RHSA-2015-0215.html
Comment 6 errata-xmlrpc 2015-02-11 15:26:32 EST 
This issue has been addressed in the following products:

  JBEAP 6.3.z for RHEL 6

Via RHSA-2015:0217 https://rhn.redhat.com/errata/RHSA-2015-0217.html
Comment 7 errata-xmlrpc 2015-02-11 15:28:00 EST 
This issue has been addressed in the following products:

  JBEAP 6.3.z for RHEL 5

Via RHSA-2015:0216 https://rhn.redhat.com/errata/RHSA-2015-0216.html
Comment 8 errata-xmlrpc 2015-02-11 16:14:37 EST 
This issue has been addressed in the following products:

  JBEAP 6.3.z for RHEL 7

Via RHSA-2015:0218 https://rhn.redhat.com/errata/RHSA-2015-0218.html
Comment 9 Arun Babu Neelicattu 2015-02-11 20:16:48 EST 
Victims Record:

https://github.com/victims/victims-cve-db/blob/master/database/java/2014/7827.yaml
Comment 14 errata-xmlrpc 2015-04-16 12:07:37 EDT 
This issue has been addressed in the following products:

  JBoss BPM Suite 6.1.0

Via RHSA-2015:0851 https://rhn.redhat.com/errata/RHSA-2015-0851.html
Comment 15 errata-xmlrpc 2015-04-16 12:10:29 EDT 
This issue has been addressed in the following products:

  JBoss BRMS 6.1.0

Via RHSA-2015:0850 https://rhn.redhat.com/errata/RHSA-2015-0850.html
Comment 16 Chess Hazlett 2015-11-02 12:58:04 EST 
All trackers fixed/errata or resolved. Closing flaw bug.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.