Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite definition before decrypting, which allows remote attackers to force CXF to use weaker cryptographic algorithms than intended and makes it easier to decrypt communications, aka "XML Encryption backwards compatibility attack."

The remote Redhat Enterprise Linux 5 / 6 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2013:0874 advisory.

    The Enterprise Web Platform is a slimmed down profile of the JBoss     Enterprise Application Platform intended for mid-size workloads with light     and rich Java applications.

    XML encryption backwards compatibility attacks were found against various     frameworks, including Apache CXF. An attacker could force a server to use     insecure, legacy cryptosystems, even when secure cryptosystems were enabled     on endpoints. By forcing the use of legacy cryptosystems, flaws such as     CVE-2011-1096 and CVE-2011-2487 would be exposed, allowing plain text to be     recovered from cryptograms and symmetric keys. This issue affected both the     JBoss Web Services CXF (jbossws-cxf) and JBoss Web Services Native     (jbossws-native) stacks. (CVE-2012-5575)

    Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and Juraj     Somorovsky of Ruhr-University Bochum for reporting this issue.

    If you are using jbossws-cxf, then automatic checks to prevent this flaw     are only run when WS-SecurityPolicy is used to enforce security     requirements. It is best practice to use WS-SecurityPolicy to enforce     security requirements.

    If you are using jbossws-native, the fix for this flaw is implemented by     two new configuration parameters in the 'encryption' element. This element     can be a child of 'requires' in both client and server wsse configuration     descriptors (set on a per-application basis via the application's     jboss-wsse-server.xml and jboss-wsse-client.xml files). The new attributes     are 'algorithms' and 'keyWrapAlgorithms'. These attributes should contain a     blank space or comma separated list of algorithm IDs that are allowed for     the encrypted incoming message, both for encryption and private key     wrapping. For backwards compatibility, no algorithm checks are performed by     default 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=rsa_oaep

    Specifies that incoming messages are required to be encrypted, and that the     only permitted encryption algorithms are AES-192 and 256 in GCM mode, and     RSA-OAEP only for key wrapping.

    Before performing any decryption, the jbossws-native stack will verify that     each algorithm specified in the incoming messages is included in the     allowed algorithms lists from these new encryption element attributes. The     algorithm values to be used for 'algorithms' and 'keyWrapAlgorithms' are     the same as for 'algorithm' and 'keyWrapAlgorithm' in the 'encrypt'     element.

    Warning: Before applying this update, back up your existing JBoss     Enterprise Web Platform installation (including all applications and     configuration files).

    All users of JBoss Enterprise Web Platform 5.2.0 on Red Hat Enterprise     Linux 4, 5, and 6 are advised to upgrade to these updated packages. The     JBoss server process must be restarted for the update to take effect.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of JBoss Enterprise Portal Platform on the remote system is affected by the following issues:

  - A flaw in CSRF prevention filter in JBoss Web could allow     remote attackers to bypass the cross-site request forgery     (CSRF) protection mechanism via a request that lacks a     session identifier. (CVE-2012-4431)

  - A flaw that occurs when the COOKIE session tracking     method is used can allow attackers to hijack users'     sessions. (CVE-2012-4529)

  - A flaw that occurs when multiple applications use the     same custom authorization module class name can allow a     local attacker to deploy a malicious application that     overrides the custom authorization modules provided by     other applications. (CVE-2012-4572)

  - The framework does not verify that a specified     cryptographic algorithm is allowed by the     WS-SecurityPolicy AlgorithmSuite definition before     decrypting.  This can allow remote attackers to force     the system to use weaker cryptographic algorithms than     intended and makes it easier to decrypt communications.
    (CVE-2012-5575)

  - A flaw in PicketBox can allow local users to obtain the     admin encryption key by reading the Vault data file.
    (CVE-2013-1921)

  - A session fixation flaw was found in the     FormAuthenticator module. (CVE-2013-2067)

  - A flaw that occurs when a JGroups channel was started     results in the JGroups diagnostics service being enabled     by default with no authentication via IP multicast. A     remote attacker can make use of this flaw to read     diagnostics information. (CVE-2013-2102)

  - A flaw in the StAX parser implementation can allow     remote attackers to cause a denial of service via     crafted XML. (CVE-2013-2160)

  - A flaw in Apache Santuario XML Security can allow     context-dependent attackers to spoof an XML Signature     by using the CanonicalizationMethod parameter to     specify an arbitrary weak algorithm. (CVE-2013-2172)

  - A flaw in JGroup's DiagnosticsHandler can allow remote     attackers to obtain sensitive information and execute     arbitrary code by re-using valid credentials.
    (CVE-2013-4112)

  - A flaw in the manner in which authenticated connections     were cached on the server by remote-naming can allow     remote attackers to hijack sessions by using a remoting     client. (CVE-2013-4128)

  - A flaw in the manner in which connections for EJB     invocations were cached on the server can allow remote     attackers to hijack sessions by using an EJB client.
    (CVE-2013-4213)

The version of JBoss Enterprise Application Platform 6.0.1 running on the remote system is vulnerable to the following issues:

  - A man-in-the-middle attack is possible when applications     running on JBoss Web use the COOKIE session tracking     method. The flaw is in the     org.apache.catalina.connector.Response.encodeURL()     method. By making use of this, an attacker could obtain     a user's jsessionid and hijack their session.
    (CVE-2012-4529)

  - If multiple applications used the same custom     authorization module class name, a local attacker could     deploy a malicious application authorization module that     would permit or deny user access. (CVE-2012-4572)

  - XML encryption backwards compatibility attacks could     allow an attacker to force a server to use insecure     legacy cryptosystems. (CVE-2012-5575)

  - A NULL pointer dereference flaw could allow a malicious     OCSP to crash applications performing OCSP verification.
    (CVE-2013-0166)

  - An OpenSSL leaks timing information issue exists that     could allow a remote attacker to retrieve plaintext     from the encrypted packets. (CVE-2013-0169)

  - The JBoss Enterprise Application Platform administrator     password and the sucker password are stored in a world-     readable, auto-install XML file created by the GUI     installer. (CVE-2013-0218)

  - Tomcat incorrectly handles certain authentication     requests. A remote attacker could use this flaw to     inject a request that would get executed with a victim's     credentials. (CVE-2013-2067)

Updated packages for JBoss Enterprise Application Platform 5.2.0 which fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.

The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

JBoss Enterprise Application Platform is a platform for Java applications, which integrates the JBoss Application Server with JBoss Hibernate and JBoss Seam.

XML encryption backwards compatibility attacks were found against various frameworks, including Apache CXF. An attacker could force a server to use insecure, legacy cryptosystems, even when secure cryptosystems were enabled on endpoints. By forcing the use of legacy cryptosystems, flaws such as CVE-2011-1096 and CVE-2011-2487 would be exposed, allowing plain text to be recovered from cryptograms and symmetric keys. This issue affected both the JBoss Web Services CXF (jbossws-cxf) and JBoss Web Services Native (jbossws-native) stacks.
(CVE-2012-5575)

Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and Juraj Somorovsky of Ruhr-University Bochum for reporting this issue.

If you are using jbossws-cxf, then automatic checks to prevent this flaw are only run when WS-SecurityPolicy is used to enforce security requirements. It is best practice to use WS-SecurityPolicy to enforce security requirements.

If you are using jbossws-native, the fix for this flaw is implemented by two new configuration parameters in the 'encryption' element. This element can be a child of 'requires' in both client and server wsse configuration descriptors (set on a per-application basis via the application's jboss-wsse-server.xml and jboss-wsse-client.xml files).
The new attributes are 'algorithms' and 'keyWrapAlgorithms'. These attributes should contain a blank space or comma separated list of algorithm IDs that are allowed for the encrypted incoming message, both for encryption and private key wrapping. For backwards compatibility, no algorithm checks are performed by default 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='rsa_oaep'

Specifies that incoming messages are required to be encrypted, and that the only permitted encryption algorithms are AES-192 and 256 in GCM mode, and RSA-OAEP only for key wrapping.

Before performing any decryption, the jbossws-native stack will verify that each algorithm specified in the incoming messages is included in the allowed algorithms lists from these new encryption element attributes. The algorithm values to be used for 'algorithms' and 'keyWrapAlgorithms' are the same as for 'algorithm' and 'keyWrapAlgorithm' in the 'encrypt' element.

Warning: Before applying this update, back up your existing JBoss Enterprise Application Platform installation (including all applications and configuration files).

All users of JBoss Enterprise Application Platform 5.2.0 on Red Hat Enterprise Linux 4, 5, and 6 are advised to upgrade to these updated packages. The JBoss server process must be restarted for the update to take effect.

Updated JBoss Enterprise Application Platform 6.1.0 packages that fix three security issues, various bugs, and add enhancements are now available for Red Hat Enterprise Linux 5.

The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7.

This release serves as a replacement for JBoss Enterprise Application Platform 6.0.1, and includes bug fixes and enhancements. Refer to the 6.1.0 Release Notes for information on the most significant of these changes, available shortly from https://access.redhat.com/site/documentation/

Security fixes :

XML encryption backwards compatibility attacks were found against various frameworks, including Apache CXF. An attacker could force a server to use insecure, legacy cryptosystems, even when secure cryptosystems were enabled on endpoints. By forcing the use of legacy cryptosystems, flaws such as CVE-2011-1096 and CVE-2011-2487 would be exposed, allowing plain text to be recovered from cryptograms and symmetric keys. (CVE-2012-5575)

Note: Automatic checks to prevent CVE-2012-5575 are only run when WS-SecurityPolicy is used to enforce security requirements. It is best practice to use WS-SecurityPolicy to enforce security requirements.

When applications running on JBoss Web used the COOKIE session tracking method, the org.apache.catalina.connector.Response.encodeURL() method returned the URL with the jsessionid appended as a query string parameter when processing the first request of a session. An attacker could possibly exploit this flaw by performing a man-in-the-middle attack to obtain a user's jsessionid and hijack their session, or by extracting the jsessionid from log files. Note that no session tracking method is used by default, one must be configured. (CVE-2012-4529)

If multiple applications used the same custom authorization module class name, and provided their own implementations of it, the first application to be loaded will have its implementation used for all other applications using the same custom authorization module class name. A local attacker could use this flaw to deploy a malicious application that provides implementations of custom authorization modules that permit or deny user access according to rules supplied by the attacker. (CVE-2012-4572)

Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and Juraj Somorovsky of Ruhr-University Bochum for reporting CVE-2012-5575.
CVE-2012-4572 was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team.

Warning: Before applying this update, back up your existing JBoss Enterprise Application Platform installation and deployed applications. Refer to the Solution section for further details.

All users of JBoss Enterprise Application Platform 6.0.1 on Red Hat Enterprise Linux 5 are advised to upgrade to these updated packages.
The JBoss server process must be restarted for the update to take effect.

Updated JBoss Enterprise Application Platform 6.1.0 packages that fix three security issues, various bugs, and add enhancements are now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7.

This release serves as a replacement for JBoss Enterprise Application Platform 6.0.1, and includes bug fixes and enhancements. Refer to the 6.1.0 Release Notes for information on the most significant of these changes, available shortly from https://access.redhat.com/site/documentation/

Security fixes :

XML encryption backwards compatibility attacks were found against various frameworks, including Apache CXF. An attacker could force a server to use insecure, legacy cryptosystems, even when secure cryptosystems were enabled on endpoints. By forcing the use of legacy cryptosystems, flaws such as CVE-2011-1096 and CVE-2011-2487 would be exposed, allowing plain text to be recovered from cryptograms and symmetric keys. (CVE-2012-5575)

Note: Automatic checks to prevent CVE-2012-5575 are only run when WS-SecurityPolicy is used to enforce security requirements. It is best practice to use WS-SecurityPolicy to enforce security requirements.

When applications running on JBoss Web used the COOKIE session tracking method, the org.apache.catalina.connector.Response.encodeURL() method returned the URL with the jsessionid appended as a query string parameter when processing the first request of a session. An attacker could possibly exploit this flaw by performing a man-in-the-middle attack to obtain a user's jsessionid and hijack their session, or by extracting the jsessionid from log files. Note that no session tracking method is used by default, one must be configured. (CVE-2012-4529)

If multiple applications used the same custom authorization module class name, and provided their own implementations of it, the first application to be loaded will have its implementation used for all other applications using the same custom authorization module class name. A local attacker could use this flaw to deploy a malicious application that provides implementations of custom authorization modules that permit or deny user access according to rules supplied by the attacker. (CVE-2012-4572)

Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and Juraj Somorovsky of Ruhr-University Bochum for reporting CVE-2012-5575.
CVE-2012-4572 was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team.

Warning: Before applying this update, back up your existing JBoss Enterprise Application Platform installation and deployed applications. Refer to the Solution section for further details.

All users of JBoss Enterprise Application Platform 6.0.1 on Red Hat Enterprise Linux 6 are advised to upgrade to these updated packages.
The JBoss server process must be restarted for the update to take effect.

ID	Name	Product	Family	Severity
210215	RHEL 5 / 6 : JBoss Enterprise Web Platform 5.2.0 (RHSA-2013:0874)	Nessus	Red Hat Local Security Checks	medium
72237	JBoss Portal 6.1.0 Update (RHSA-2013:1437)	Nessus	Red Hat Local Security Checks	high
66971	JBoss Enterprise Application Platform 6.1.0 Update (RHSA-2013:0833)	Nessus	Red Hat Local Security Checks	high
66662	RHEL 5 / 6 : JBoss EAP (RHSA-2013:0873)	Nessus	Red Hat Local Security Checks	medium
66523	RHEL 5 : JBoss EAP (RHSA-2013:0839)	Nessus	Red Hat Local Security Checks	medium
66522	RHEL 6 : JBoss EAP (RHSA-2013:0834)	Nessus	Red Hat Local Security Checks	medium

Detections

Analytics

CVE-2012-5575

medium

Tenable Plugins

medium

high

high

medium

medium

medium