GitHub user djoelz opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/216
Fixing insecure CORS filter settings
Fixing cross origin bug for rest calls that allow a malicious user to issue
requests from a site other than the zeppelin server.
Adding unit tests and a dependency to mockito to the server project (please
comment if that is ok or if there is another preferred mocking framework).
Also upgrading the servelet version from 2.5 to 3.0 as this also fixes a
security vulnerability with respect to httonly cookies.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/djoelz/incubator-zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/216.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #216
----
commit cecbab8fbb82fde0138d8bff11e16c2b220b0c16
Author: joelz <[email protected]>
Date: 2015-08-16T10:08:38Z
Fixing cross origin bug for rest calls that allow a malicious user to issue
requests from a site other than the zeppelin server.
Adding unit tests and a dependency to mockito to the server project (please
comment if that is ok or if there is another preferred mocking framework).
Also upgrading the servelet version from 2.5 to 3.0 as this also fixes a
security vulnerability with respect to httonly cookies.
commit df324dea2ff81017c2b9a306b082cdcea5b80ecb
Author: joelz <[email protected]>
Date: 2015-08-16T10:10:28Z
Fixing cross origin bug for rest calls that allow a malicious user to issue
requests from a site other than the zeppelin server.
Adding unit tests and a dependency to mockito to the server project (please
comment if that is ok or if there is another preferred mocking framework).
Also upgrading the servelet version from 2.5 to 3.0 as this also fixes a
security vulnerability with respect to httonly cookies.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
