[
https://issues.apache.org/jira/browse/ZOOKEEPER-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andor Molnar resolved ZOOKEEPER-2590.
-------------------------------------
Fix Version/s: 3.10.0
3.7.3
3.8.4
3.9.2
Assignee: Andor Molnar (was: Ling Mao)
Resolution: Fixed
> exists() should check read ACL permission
> -----------------------------------------
>
> Key: ZOOKEEPER-2590
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2590
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Edward Ribeiro
> Assignee: Andor Molnar
> Priority: Major
> Labels: acl, pull-request-available, security
> Fix For: 3.10.0, 3.7.3, 3.8.4, 3.9.2
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> As hinted
> [here|https://github.com/apache/zookeeper/blob/master/src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java#L298],
> even if a parent znode path has restricted READ access it's possible to
> issue an exists() operation on any child znode of that given path.
> For example, the snippet below doesn't throw {{NoAuthExceptio}}, even tough
> it removes ACL rights to "/":
> {code}
> zk.create("/a", null, Ids.OPEN_ACL_UNSAFE, CreateMode.PERSISTENT);
> ArrayList<ACL> acls = new ArrayList<>();
> acls.add(new ACL(0, Ids.ANYONE_ID_UNSAFE));
> zk.setACL("/", acls, -1);
> Stat r = zk.exists("/a", false);
> {code}
> Also, in the above example, what if the removed READ access for "/a"? Should
> we allow a call to exists("/a") to succeed even if it returns the znode
> metadata info?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
