First published: Mon Aug 07 2017(Updated: )
Log4j is a tool to help the programmer output log statements to a variety of output targets.<br>Security Fix(es):<br><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>
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/log4j | <1.2.17-16.el7_4 | 1.2.17-16.el7_4 |
redhat/log4j | <1.2.17-16.el7_4 | 1.2.17-16.el7_4 |
redhat/log4j-javadoc | <1.2.17-16.el7_4 | 1.2.17-16.el7_4 |
redhat/log4j-manual | <1.2.17-16.el7_4 | 1.2.17-16.el7_4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2017:2423 is classified as important.
To fix RHSA-2017:2423, you should upgrade to log4j version 1.2.17-16.el7_4 or later.
RHSA-2017:2423 addresses a remote logging vulnerability in log4j that allows deserialization of log events.
The affected packages for RHSA-2017:2423 include log4j, log4j-javadoc, and log4j-manual.
RHSA-2017:2423 is applicable to users running Red Hat systems with the affected log4j versions.