CVE-2019-17571criticalCWE-502

CVE-2019-17571: critical vulnerability in Apache Software Foundation Log4j

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

62Vexday Risk Score

Keep watching. It has a public proof of concept.

ssvc Attendcvss 9.8epss 70%
from disclosure to weapon5 days
Published on NVDDec 20
1st PoC+5d
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Affected
3 products
Red Hat Enterprise Linux 5 · Red Hat JBoss BRMS 5 · Red Hat JBoss SOA Platform 5
workaround: Please note that the Log4j upstream strongly recommends against using the SerializedLayout with the SocketAppenders. Customers may mitigate this issue by removing the SocketServer class outright…
Fixed
27 products (119 components)
Red Hat JBoss Web Server 3.1 for RHEL 6 · Red Hat JBoss Web Server 3.1 for RHEL 7 · Red Hat Enterprise Linux Server Optional (v. 6 ELS) · Red Hat Enterprise Linux Server (v. 6 ELS) · Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server · and others 22
Not affected
19 products (32 components) — because the vulnerable code is not present in the product
Red Hat Software Collections · Red Hat Enterprise Linux 8 · Red Hat Fuse 7 · Red Hat Mobile Application Platform 4 · Red Hat OpenShift Application Runtimes · and others 14
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.