You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2019/12/03 11:20:00 UTC
[jira] [Resolved] (SOLR-13982) set security-related http response
headers by default
[ https://issues.apache.org/jira/browse/SOLR-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved SOLR-13982.
--------------------------------
Resolution: Fixed
thanks for looking at the patch ishan! I hope we find a way to fix SOLR-13987 so that modern browser security actually works for us :(
> 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
> Fix For: 8.4
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org