SAICHARAN REDDY KOTLA created ZOOKEEPER-3990:
------------------------------------------------

             Summary: Log4j 1.2.17 used by zookeeper 3.6.1 is vulnerable to 
CVE-2019-17571
                 Key: ZOOKEEPER-3990
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3990
             Project: ZooKeeper
          Issue Type: Bug
    Affects Versions: 3.6.2, 3.6.1
            Reporter: SAICHARAN REDDY KOTLA


Hello everyone,

I work for a product which uses apache/zookeeper 3.6.1.  We scanned our product 
with a security scanner which reported CVE-2019-17571. 

After analysis we found that this vulnerability is coming from zookeeper 3.6.1 
because of direct dependency on log4j 1.2.17. 

Statement regarding 1.x version of log4j from [official 
|http://logging.apache.org/log4j/1.2/] site:
{quote}A security vulnerability, CVE-2019-17571 has been identified against 
Log4j 1. Log4j includes a SocketServer that accepts serialized log events and 
deserializes them without verifying whether the objects are allowed or not. 
This can provide an attack vector that can be expoited. Since Log4j 1 is no 
longer maintained this issue will not be fixed. Users are urged to upgrade to 
Log4j 2.x
{quote}
Could you please share your rationale on not upgrading log4j to 2.x



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to