[ https://issues.apache.org/jira/browse/SOLR-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986808#comment-16986808 ]
ASF subversion and git services commented on SOLR-13987: -------------------------------------------------------- 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. > fix admin UI to not rely on javascript eval() > --------------------------------------------- > > Key: SOLR-13987 > URL: https://issues.apache.org/jira/browse/SOLR-13987 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Robert Muir > Priority: Major > > Followup from SOLR-13982: currently any CSP is weak because it must allow > this eval: means arbitrary javascript can still be executed. > Let's fix the admin UI to not require eval so it can be disabled by the > browser. -- 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