[
https://issues.apache.org/jira/browse/HIVE-8893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218512#comment-14218512
]
Szehon Ho commented on HIVE-8893:
---------------------------------
Hi Prasad, sorry about that, was looking at the patch again and whitespace is
still there on the latest patch, I didnt notice it.
Also I took a look and its inconsistent in setupBlockedUdfs() to check for
empty for black and white list. While we are changing, can we also use the
guava splitter with omitEmptyString() argument for this situation, so the logic
is cleaner? Again sorry I didnt look that closely before.
> Implement whitelist for builtin UDFs to avoid untrused code execution in
> multiuser mode
> ---------------------------------------------------------------------------------------
>
> Key: HIVE-8893
> URL: https://issues.apache.org/jira/browse/HIVE-8893
> Project: Hive
> Issue Type: Bug
> Components: Authorization, HiveServer2, SQL
> Affects Versions: 0.14.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: 0.15.0
>
> Attachments: HIVE-8893.3.patch, HIVE-8893.4.patch, HIVE-8893.5.patch
>
>
> The udfs like reflect() or java_method() enables executing a java method as
> udf. While this offers lot of flexibility in the standalone mode, it can
> become a security loophole in a secure multiuser environment. For example, in
> HiveServer2 one can execute any available java code with user hive's
> credentials.
> We need a whitelist and blacklist to restrict builtin udfs in Hiveserver2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
