https://bugzilla.redhat.com/show_bug.cgi?id=1501529

--- Comment #11 from Chess Hazlett chazlett@redhat.com --- Statement:

The following products are not affected by this flaw, as they do not use the vulnerable functionality of either aspect of the issue. Red Hat JBoss Enterprise Application Platform 6 Red Hat JBoss BPM Suite Red Hat JBoss BRMS

Red Hat JBoss Enterprise Application Platform 7 is not affected by this flaw. However, it does ship the vulnerable Lucene class in a dependency to another component. Customers who reuse the lucene-queryparser jar in their applications may be vulnerable to the External Entity Expansion aspect of this flaw. This will be patched in a forthcoming release.

Red Hat JBoss Fuse is not affected by this flaw, as it does not use the vulnerable functionality of either aspect of this flaw. Fuse customers who may be running external Solr servers, while not affected from the Fuse side, are advised to secure their Solr servers as recommended in the mitigation provided.

The following products ship only the Lucene components relevant to this flaw, and are not vulnerable to the second portion of the vulnerability, the code execution exploit. As such, the impact of this flaw has been determined to be Moderate for these respective products: Red Hat JBoss Data Grid 7 Red Hat Single Sign-On 7

Red Hat JBoss Portal Platform 6 ships only the Solr components relevant to this flaw, and is not vulnerable to the first portion of the vulnerability, the external entity expansion. As such, the impact of this flaw has been determined to be Moderate for this product. Customers are advised to disable changes to the Config API until a component fix is available; see mitigation text for details.