[
https://issues.apache.org/jira/browse/HBASE-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163439#comment-15163439
]
Ted Yu commented on HBASE-15187:
--------------------------------
I went through some posts on using ESAPI to counter CSRF attack:
http://www.jtmelton.com/2010/05/16/the-owasp-top-ten-and-esapi-part-6-cross-site-request-forgery-csrf/
http://stackoverflow.com/questions/22555110/csrf-cross-site-request-forgery-protection-in-spring-mvc
The CSRF prevention it offers requires an exchange of a unique token value.
While the hadoop filter only requires the presence of a header in the request.
The need for a unique token value means that the server side needs to generate
nonces and remember them so that they'll be considered valid on subsequent
requests. In my opinion this would be a much more intrusive change than what
the hadoop filter does.
> Integrate CSRF prevention filter to REST gateway
> ------------------------------------------------
>
> Key: HBASE-15187
> URL: https://issues.apache.org/jira/browse/HBASE-15187
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: HBASE-15187.v1.patch, HBASE-15187.v2.patch,
> HBASE-15187.v3.patch, HBASE-15187.v4.patch, HBASE-15187.v5.patch,
> HBASE-15187.v6.patch, HBASE-15187.v7.patch, HBASE-15187.v8.patch
>
>
> HADOOP-12691 introduced a filter in Hadoop Common to help REST APIs guard
> against cross-site request forgery attacks.
> This issue tracks the integration of that filter into HBase REST gateway.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
