[ 
https://issues.apache.org/jira/browse/SOLR-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986807#comment-16986807
 ] 

ASF subversion and git services commented on SOLR-13982:
--------------------------------------------------------

Commit 55b77358cff29ae1ebf8d8bcab754450e14b1a0a in lucene-solr's branch 
refs/heads/branch_8x from Robert Muir
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=55b7735 ]

SOLR-13982: set security-related http response headers by default

Unfortunately, as a first start this is very weak protection against
e.g. XSS.  This is because some 'unsafe-xxx' rules must be present due
to the insecurity of angular JS: Until SOLR-13987 is fixed, XSS & co are
still easy.


> set security-related http response headers by default
> -----------------------------------------------------
>
>                 Key: SOLR-13982
>                 URL: https://issues.apache.org/jira/browse/SOLR-13982
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Robert Muir
>            Priority: Major
>         Attachments: SOLR-13982.patch
>
>
> Solr server should set some best practice http security response headers, to 
> e.g. protect users of the admin ui against XSS/injection/clickjacking/etc
> * Content-Security-Policy 
> * X-Content-Type-Options
> * X-XSS-Protection
> * X-Frame-Options
> Disabling inline javascript is important, so that e.g. if there is a bug then 
> injected code doesn't get executed. Unfortunately the current admin UI 
> dangerously relies on {{eval}}, so for now {{unsafe-eval}} must be allowed so 
> that everything still works. This should really be cleaned up, i have the 
> feeling as long as it works this way, that you can still execute stuff.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to