No authentication/authorization is enforced when a server attempts to join a quorum in Apache ZooKeeper before 3.4.10, and 3.5.0-alpha through 3.5.3-beta. As a result an arbitrary end point could join the cluster and begin propagating counterfeit changes to the leader.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2018-8012 from the MITRE CVE dictionary dictionary and NIST NVD.
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.
NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.
CVSS3 Base Score | 7.4 |
---|---|
CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Attack Vector | Network |
Attack Complexity | High |
Privileges Required | None |
User Interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity Impact | High |
Availability Impact | None |
Platform | Package | State |
---|---|---|
Red Hat OpenShift Application Runtimes 1.0 | vertx | Not affected |
Red Hat JBoss Fuse Service Works 6 | zookeeper | Not affected |
Red Hat JBoss Fuse 7 | zookeeper | Not affected |
Red Hat JBoss Fuse 6 | zookeeper | Will not fix |
Red Hat JBoss Data Virtualization 6 | zookeeper | Under investigation |
Red Hat JBoss BRMS 6 | zookeeper | Not affected |
Red Hat JBoss BPMS 6 | zookeeper | Not affected |
Red Hat JBoss A-MQ 6 | zookeeper | Will not fix |