[
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868762#comment-15868762
]
ASF GitHub Bot commented on ZOOKEEPER-2693:
-------------------------------------------
Github user afine commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/179#discussion_r101403760
--- Diff: src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml ---
@@ -2125,6 +2151,18 @@ server.3=zoo3:2888:3888</programlisting>
usage limit that would cause the system to swap.</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>Publicly accessible deployment</term>
+
+ <listitem>
+ <para>ZooKeeper was not designed to be opened to the outside
world. A ZooKeeper
--- End diff --
Both of these sentences are a little bit redundant, perhaps this can be
simplified to:
A ZooKeeper ensemble is expected to operate in a trusted computing
environment. It is thus recommended to deploy ZooKeeper behind a firewall.
> 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
>
>
> 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)
