remote code execution due to insecure XML deserialization
CVE: CVE-2013-7285
Component: XStream
CWE: CWE-94
Severity: Important
Release date: 2013-12-22T00:00:00+00:00

It was found that XStream could deserialize arbitrary user-supplied XML content, representing objects of any type. A remote attacker able to pass XML to XStream could use this flaw to perform a variety of attacks, including remote code execution in the context of the server running the XStream application.


Remediation:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/site/articles/11258
The References section of this erratum contains a download link (you must
log in to download the update).
The References section of this erratum contains a download link (you must
log in to download the update). Before applying the update, back up your
existing Red Hat JBoss BRMS installation (including its databases,
applications, configuration files, and so on).

Note that it is recommended to halt the Red Hat JBoss BRMS server by
stopping the JBoss Application Server process before installing this
update, and then after installing the update, restart the Red Hat JBoss
BRMS server by starting the JBoss Application Server process.
The References section of this erratum contains download links (you must
log in to download the update).
The References section of this erratum contains download links (you must
log in to download the updates). Before applying the update, back up your
existing installation, including all applications, configuration files,
databases and database settings, and so on.

It is recommended to halt the server by stopping the JBoss Application
Server process before installing this update, and then after installing the
update, restart the server by starting the JBoss Application Server process.

The fix for CVE-2013-6468 enables the Java Security Manager (JSM) to
sandbox the evaluation of MVEL expressions. This introduces performance
degradation in high load environments. The following ways of running Red
Hat JBoss BPM Suite are considered secure while mitigating performance
degradation:

1. In high load environments where performance is critical, it is
recommended to only deploy applications that have been developed on other
systems and properly reviewed. It is also recommended not to create any
users with the Analyst role on such systems. If these safeguards are
followed, it is safe to leave JSM disabled on these systems so it does not
introduce any performance degradation.

2. In testing and development environments without high loads, or in
environments where rule authoring is exposed to external networks, it is
recommended to have JSM enabled in order to achieve security benefits of
properly sandboxed evaluation of MVEL expressions.

Allowing users with the Analyst role to log in to the Business Central
console when JSM is disabled is not secure and not recommended.
The References section of this erratum contains download links (you must
log in to download the updates). Before applying the update, back up your
existing installation, including all applications, configuration files,
databases and database settings, and so on.

It is recommended to halt the server by stopping the JBoss Application
Server process before installing this update, and then after installing the
update, restart the server by starting the JBoss Application Server process.

The fix for CVE-2013-6468 enables the Java Security Manager (JSM) to
sandbox the evaluation of MVEL expressions. This introduces performance
degradation in high load environments. The following ways of running Red
Hat JBoss BRMS are considered secure while mitigating performance
degradation:

1. In high load environments where performance is critical, it is
recommended to only deploy applications that have been developed on other
systems and properly reviewed. It is also recommended not to create any
users with the Analyst role on such systems. If these safeguards are
followed, it is safe to leave JSM disabled on these systems so it does not
introduce any performance degradation.

2. In testing and development environments without high loads, or in
environments where rule authoring is exposed to external networks, it is
recommended to have JSM enabled in order to achieve security benefits of
properly sandboxed evaluation of MVEL expressions.

Allowing users with the Analyst role to log in to the Business Central
console when JSM is disabled is not secure and not recommended.
The References section of this erratum contains a download link (you must
log in to download the update). Before applying this update, back up your
existing JBoss Data Grid installation.
The References section of this erratum contains a download link (you must
log in to download the updates). Before applying the updates, back up your
existing installation, including all applications, configuration files,
databases and database settings, and so on.

It is recommended to halt the server by stopping the JBoss Application
Server process before installing this update, and then after installing the
update, restart the server by starting the JBoss Application Server
process.
The References section of this erratum contains a download link (you must
log in to download the updates). Before applying the updates, back up your
existing installation, including all applications, configuration files,
databases and database settings, and so on.

It is recommended to halt the server by stopping the JBoss Application
Server process before installing this update, and then after installing the
update, restart the server by starting the JBoss Application
Server process.
The References section of this erratum contains a download link (you must
log in to download the update). Before applying the update, back up all
applications deployed on JBoss Enterprise Portal Platform, along with all
customized configuration files, and any databases and database settings.

Note that it is recommended to halt the JBoss Enterprise Portal Platform
server by stopping the JBoss Application Server process before installing
this update, and then after installing the update, restart the JBoss
Enterprise Portal Platform server by starting the JBoss Application Server
process.
All users of Red Hat JBoss Portal 6.1.1 as provided from the Red Hat
Customer Portal are advised to upgrade to Red Hat JBoss Portal 6.2.0.

The References section of this erratum contains a download link (you must
log in to download the update). Before applying the update, back up all
applications deployed on JBoss Enterprise Portal Platform, along with all
customized configuration files, and any databases and database settings.
The References section of this erratum contains a download link (you must
log in to download the update). Before applying the update, back up your
existing Red Hat JBoss SOA Platform installation (including its databases,
applications, configuration files, and so on).

Note that it is recommended to halt the Red Hat JBoss SOA Platform server
by stopping the JBoss Application Server process before installing this
update, and then after installing the update, restart the Red Hat JBoss SOA
Platform server by starting the JBoss Application Server process.