lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (SOLR-13982) set security-related http response headers by default
Date Tue, 03 Dec 2019 11:18:00 GMT


ASF subversion and git services commented on SOLR-13982:

Commit c8c9c1002353db3b8a4d89d21849bf67bc4f0931 in lucene-solr's branch refs/heads/master
from Robert Muir
[;h=c8c9c10 ]

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:
>             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

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message