logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <mattsic...@apache.org>
Subject Fwd: CVE-2017-5645: Apache Log4j socket receiver deserialization vulnerability
Date Mon, 17 Apr 2017 15:18:35 GMT
---------- Forwarded message ----------
From: Matt Sicker <mattsicker@apache.org>
Date: 17 April 2017 at 10:17
Subject: CVE-2017-5645: Apache Log4j socket receiver deserialization
vulnerability
To: dev@logging.apache.org, security <security@apache.org>, "Almeida De
Macedo, Marcio" <Marcio.AlmeidaDeMacedo@team.telstra.com>,
oss-security@lists.openwall.com, bugtraq@securityfocus.com


CVE-2017-5645: Apache Log4j socket receiver deserialization vulnerability

Severity: High

CVSS Base Score: 7.5 (AV:N/AC:L/Au:N/C:P/I:P/A:P)

Vendor: The Apache Software Foundation

Versions Affected: all versions from 2.0-alpha1 to 2.8.1

Description: When using the TCP socket server or UDP socket server to
receive serialized log events from another application, a specially crafted
binary payload can be sent that, when deserialized, can execute arbitrary
code.

Mitigation: Java 7+ users should migrate to version 2.8.2 or avoid using
the socket server classes. Java 6 users should avoid using the TCP or UDP
socket server classes, or they can manually backport the security fix from
2.8.2: <https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.gi
t;h=5dcc192>

Credit: This issue was discovered by Marcio Almeida de Macedo of Red Team
at Telstra

References: <https://issues.apache.org/jira/browse/LOG4J2-1863>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message