RHSA-2013:1006: Important: Red Hat JBoss BRMS 5.3.1 update

Red Hat JBoss BRMS is a business rules management system for themanagement, storage, creation, modification, and deployment of JBoss Rules.This roll up patch serves as a cumulative upgrade for Red Hat JBoss BRMS5.3.1. It includes various bug fixes. The following securityissues are also fixed with this release:XML encryption backwards compatibility attacks were found against variousframeworks, including Apache CXF. An attacker could force a server to useinsecure, legacy cryptosystems, even when secure cryptosystems were enabledon endpoints. By forcing the use of legacy cryptosystems, flaws such asCVE-2011-1096 and CVE-2011-2487 would be exposed, allowing plain text to berecovered from cryptograms and symmetric keys. This issue affected both theJBoss Web Services CXF (jbossws-cxf) and JBoss Web Services Native(jbossws-native) stacks. (CVE-2012-5575)If you are using jbossws-cxf, then automatic checks to prevent this flaware only run when WS-SecurityPolicy is used to enforce securityrequirements. It is best practice to use WS-SecurityPolicy to enforcesecurity requirements.If you are using jbossws-native, the fix for this flaw is implemented bytwo new configuration parameters in the 'encryption' element. This elementcan be a child of 'requires' in both client and server wsse configurationdescriptors (set on a per-application basis via the application'sjboss-wsse-server.xml and jboss-wsse-client.xml files). The new attributesare 'algorithms' and 'keyWrapAlgorithms'. These attributes should contain ablank space or comma separated list of algorithm IDs that are allowed forthe encrypted incoming message, both for encryption and private keywrapping. For backwards compatibility, no algorithm checks are performed bydefault for empty lists or missing attributes.For example (do not include the line break in your configuration):encryption algorithms="aes-192-gcm aes-256-gcm"keyWrapAlgorithms="rsaoaep"Specifies that incoming messages are required to be encrypted, and that theonly permitted encryption algorithms are AES-192 and 256 in GCM mode, andRSA-OAEP only for key wrapping.Before performing any decryption, the jbossws-native stack will verify thateach algorithm specified in the incoming messages is included in theallowed algorithms lists from these new encryption element attributes. Thealgorithm values to be used for 'algorithms' and 'keyWrapAlgorithms' arethe same as for 'algorithm' and 'keyWrapAlgorithm' in the 'encrypt'element.The Jakarta Commons HttpClient component did not verify that the serverhostname matched the domain name in the subject's Common Name (CN) orsubjectAltName field in X.509 certificates. This could allow aman-in-the-middle attacker to spoof an SSL server if they had a certificatethat was valid for any domain name. (CVE-2012-5783)Multiple weaknesses were found in the JBoss Web DIGEST authenticationimplementation, effectively reducing the security normally provided byDIGEST authentication. A remote attacker could use these flaws to performreplay attacks in some circumstances. (CVE-2012-5885, CVE-2012-5886,CVE-2012-5887)Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and JurajSomorovsky of Ruhr-University Bochum for reporting CVE-2012-5575.Warning: Before applying the update, back up your existing Red Hat JBossBRMS installation (including its databases, applications, configurationfiles, and so on).All users of Red Hat JBoss BRMS 5.3.1 as provided from the Red Hat CustomerPortal are advised to apply this roll up patch.