RHSA-2017:3244: Important: Red Hat JBoss Data Grid 7.1.1 security update
Red Hat JBoss Data Grid is a distributed in-memory data grid, based on Infinispan.<br>This release of Red Hat JBoss Data Grid 7.1.1 serves as a replacement for Red Hat JBoss Data Grid 7.1.0, and includes bug fixes and enhancements, which are documented in the Release Notes linked to in the References.<br>Security Fix(es):<br><li> It was found that Apache Lucene would accept an object from an unauthenticated user that could be manipulated through subsequent post requests. An attacker could use this flaw to assemble an object that could permit execution of arbitrary code if the server enabled Apache Solr's Config API. (CVE-2017-12629)</li> <li> It was found that when using remote logging with log4j socket server the log4j server would deserialize any log event received via TCP or UDP. An attacker could use this flaw to send a specially crafted log event that, during deserialization, would execute arbitrary code in the context of the logger application. (CVE-2017-5645)</li> <li> The hotrod java client in infinispan automatically deserializes bytearray message contents in certain events. A malicious user could exploit this flaw by injecting a specially-crafted serialized object to attain remote code execution or conduct other attacks. (CVE-2016-0750)</li> For more information regarding CVE-2017-12629, see the article linked in the references section.<br>Red Hat would like to thank Sebastian Olsson (TrueSec) for reporting CVE-2016-0750.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2017:3244?
The severity of RHSA-2017:3244 is classified as moderate.
What vulnerabilities are addressed in RHSA-2017:3244?
RHSA-2017:3244 addresses bug fixes and enhancements in Red Hat JBoss Data Grid 7.1.1.
How do I fix RHSA-2017:3244?
To fix RHSA-2017:3244, you should update to Red Hat JBoss Data Grid 7.1.1 or later.
Is RHSA-2017:3244 a critical issue?
RHSA-2017:3244 is not classified as a critical issue but should be addressed to ensure optimal performance.
What should I do after applying the fix for RHSA-2017:3244?
After applying the fix for RHSA-2017:3244, you should test your environment to ensure stability and performance.