[
https://issues.apache.org/jira/browse/HBASE-13768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558385#comment-14558385
]
Andrew Purtell commented on HBASE-13768:
----------------------------------------
We released temporary patch fixes provided by [~enis] as:
0.98.12.1: https://github.com/apache/hbase/commit/b0600da
1.0.1.1: https://github.com/apache/hbase/commit/f20fdb5
1.1.0.1: https://github.com/apache/hbase/commit/5b5f976
A more comprehensive fix is in the works that includes new checks in the master
for correct znode ACLs at boot, and an integration test that better verifies
correct secure integration with ZK and HDFS.
This is a blocker for all pending releases.
> ZooKeeper znodes are bootstrapped with insecure ACLs in a secure configuration
> ------------------------------------------------------------------------------
>
> Key: HBASE-13768
> URL: https://issues.apache.org/jira/browse/HBASE-13768
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1, 0.98.12.1, 1.0.1.1,
> 1.1.0.1
>
>
> A logic error causes HBase in most secure configuration deployments to handle
> its coordination state in ZooKeeper via insecure ACLs. Anyone with remote
> unauthenticated network access to the ZooKeeper quorum, which by definition
> includes all HBase clients, can make use of this opening to violate the
> operational integrity of the system. For example, critical znodes can be
> deleted, causing outages. It is possible to introduce rogue replication
> endpoints. It is possible to direct the distributed log splitting facility to
> split arbitrary files in HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
