[
https://issues.apache.org/jira/browse/SOLR-14049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437680#comment-17437680
]
Jan Høydahl commented on SOLR-14049:
------------------------------------
Coming back to this, I think we now have enough warnings in logs that your solr
is insecure, and in ref-guide about the dangers of exposing an non-secured
Solr. And I think the default {{bin/solr auth enable}} command protects
config-apis with an admin role. Only thing that lacks is to enable security by
default when installing Solr.
If you have a Solr exposed to enemies, without Auth, then it is game over, even
if we disable config API by default. So it would give a false sense of safety
to add such flags. Better educate users about securing Solr, and never ever
expose it to the world.
> Disable Config APIs by default
> ------------------------------
>
> Key: SOLR-14049
> URL: https://issues.apache.org/jira/browse/SOLR-14049
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> Spin off from SOLR-13978. This is not my proposal (I support this only
> conditionally), I'm just opening the JIRA.
> Proposal is to do this by 8.4. Reason is that Config APIs have been used in
> the past to invoke RCE vulnerabilities in some components of Solr.
> The discussion has happened in SOLR-13978. I am willing to do the work once
> we have agreement on this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
