Bug 1581542 (CVE-2018-8012)

Summary: CVE-2018-8012 zookeeper: No authentication or authorization is enforced when a server joins a quorum
Product: [Other] Security Response Reporter: Sam Fowler <sfowler>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: aileenc, alazarot, anstephe, avibelli, bgeorges, chazlett, cmoulliard, ctubbsii, drieden, etirelli, gvarsami, ibek, java-sig-commits, jbalunas, jcoleman, jolee, jpallich, jschatte, jshepherd, jstastny, kconner, krathod, kverlaen, ldimaggi, lpetrovi, lthon, mluscon, mszynkie, nwallace, paradhya, pavelp, pgallagh, rhel8-maint, rrajasek, rruss, rsynek, rwagner, rzhang, sdaley, sfowler, s, tcunning, tkirby, trogers, tstclair, vhalbert
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: zookeeper 3.4.10 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-10 10:26:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1581543, 1581544    
Bug Blocks: 1581546    

Description Sam Fowler 2018-05-23 04:02:15 UTC
Apache ZooKeeper before 3.4.10, and 3.5.0-alpha through 3.5.3-beta does not enforce any authentication/authorization when a server attempts to join a quorum. As a result an arbitrary end point could join the cluster and begin propagating counterfeit changes to the leader.


External References:

http://openwall.com/lists/oss-security/2018/05/21/6
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Server-Server+mutual+authentication
https://issues.apache.org/jira/browse/ZOOKEEPER-1045

Comment 1 Sam Fowler 2018-05-23 04:03:00 UTC
Created zookeeper tracking bugs for this issue:

Affects: fedora-all [bug 1581543]

Comment 4 Jason Shepherd 2018-05-23 06:25:13 UTC
Zookeeper is also included in vertx as a dependency of the vertx-kafka component. Setting it back to new while we investigate it it's affected or not.

[INFO] +- io.vertx:vertx-kafka-client:jar:3.5.1.redhat-003:compile
[INFO] |  +- org.apache.kafka:kafka-clients:jar:1.0.0:compile
[INFO] |  |  +- org.lz4:lz4-java:jar:1.4:compile
[INFO] |  |  \- org.xerial.snappy:snappy-java:jar:1.1.4:compile
[INFO] |  +- org.apache.kafka:kafka_2.12:jar:1.0.0:compile
[INFO] |  |  +- net.sf.jopt-simple:jopt-simple:jar:5.0.4:compile
[INFO] |  |  +- com.yammer.metrics:metrics-core:jar:2.2.0:compile
[INFO] |  |  +- com.101tec:zkclient:jar:0.10:compile
[INFO] |  |  \- org.apache.zookeeper:zookeeper:jar:3.4.10:compile

Comment 5 Jason Shepherd 2018-05-23 07:14:28 UTC
vertx-kafka-client is a component which allows vertx to talk to a kafka instance. It does not actually use zookeeper itself to form a quorom. Setting as NOTAFFECTED. ref:

https://vertx.io/docs/vertx-kafka-client/java/

Comment 6 Hooman Broujerdi 2018-05-23 23:32:28 UTC
Statement:

Zookeeper is not designed to run as a publicly available service and it always needs to be deployed and operated in a secured environment. As a result it is assumed that no zookeeper ports are available publically, so with this assumption JBoss Fuse is not affected by this issue.