Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Thu, 23 Feb 2017 01:05:44 +0000 (UTC)
From: "Michael Han (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13042793.1487043193000.38045.1487811944169@Atlassian.JIRA>
In-Reply-To: <JIRA.13042793.1487043193000@Atlassian.JIRA>
References: <JIRA.13042793.1487043193000@Atlassian.JIRA> <JIRA.13042793.1487043193979@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four
 letter words (4lw)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 23 Feb 2017 01:06:21 -0000


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879633#comment-15879633 ] 

Michael Han commented on ZOOKEEPER-2693:
----------------------------------------

bq. But for 3.5.3 releasing, we need both whitelist config and deprecating 4lw tasks together.
[~rakeshr] I am thinking we can deprecating 4lw usage for 3.5 later, it does not sound a must have for addressing the specific security concern raised in this JIRA. I think the current patch is ready to land after we figure out how to deal with isro and srvr command currently used by ZK.

> DOS attack on wchp/wchc four letter words (4lw)
> -----------------------------------------------
>
>                 Key: ZOOKEEPER-2693
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: security, server
>    Affects Versions: 3.4.0, 3.5.1, 3.5.2
>            Reporter: Patrick Hunt
>            Assignee: Michael Han
>            Priority: Blocker
>             Fix For: 3.4.10, 3.5.3
>
>         Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK client port - typically 2181. The following POC attack was recently published on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+&cd=14&hl=en&ct=clnk&gl=us
> The most straightforward way to block this attack is to not allow access to the client port to non-trusted clients - i.e. firewall the ZooKeeper service and only allow access to trusted applications using it for coordination.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)