[HDFS-10276] HDFS should not expose path info that user has no permission to see.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.4, 3.0.0-alpha1
• Component/s: fs, security
• Labels: security
• Hadoop Flags: Reviewed
• Assignee: Yuanbo Liu
• Reporter: Kevin Cox
• Created: 11/Apr/16 16:22
• Updated: 06/Mar/18 21:23
• Resolved: 27/May/16 17:26

Description

This following issue is remedied by HDFS-5802.

Given you have a file /file an existence check for the path /file/whatever will give different responses for different implementations of FileSystem.

LocalFileSystem will return false while DistributedFileSystem will throw org.apache.hadoop.security.AccessControlException: Permission denied: ..., access=EXECUTE, ...

However, HDFS-5802 may expose information about a path that user doesn't have permission to see.

For example, if the user asks for /a/b/c, but does not have permission to list /a, we should not complain about /a/b

Issue Links

• relates to: HDFS-5802 NameNode does not check for inode type before traversing down a path