[
https://issues.apache.org/jira/browse/SENTRY-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014896#comment-15014896
]
Lenni Kuff commented on SENTRY-960:
-----------------------------------
[~sravya] - I think the safest approach is to go with a whitelist approach and
consider that new commands that have been added have not been sufficiently
tested/evaluated to be considered safe to execute. The whitelist should also be
configurable so that we can unblock someone without a code change in the
future.
> Sentry no longer enforces it's whitelist
> ----------------------------------------
>
> Key: SENTRY-960
> URL: https://issues.apache.org/jira/browse/SENTRY-960
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Reporter: Ryan P
> Assignee: Sravya Tirukkovalur
> Attachments: SENTRY-960.2.patch, SENTRY-960.3.patch,
> SENTRY-960.4.patch, SENTRY-960.4.patch, SENTRY-960.5.patch,
> SENTRY-960.6.patch, SENTRY-960.7.patch, SENTRY-960.8.patch,
> SENTRY-960.9.patch, SENTRY-960.patch
>
>
> HiveSemanticAnalyzerHookContext no longer includes built-in functions as an
> input to it's Read Entities. This change hides built in functions from
> HiveAuthzBindingHook which is a huge security hole.
> Failing to enforce the whitelist will allow users to execute such functions
> as REFLECT and JAVA_METHOD.
> https://cwiki.apache.org/confluence/display/Hive/ReflectUDF
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
