janhoy commented on code in PR #80: URL: https://github.com/apache/solr-site/pull/80#discussion_r1009876752
########## content/pages/security.md: ########## @@ -7,6 +7,9 @@ template: security If you believe you have discovered a vulnerability in Solr, you may first want to consult the [list of known false positives](https://cwiki.apache.org/confluence/display/SOLR/SolrSecurity#SolrSecurity-SolrandVulnerabilityScanningTools) to make sure you are reporting a real vulnerability. Then please disclose responsibly by following [these ASF guidelines](https://www.apache.org/security/) for reporting. +The Solr PMC will not accept the output of a vulnerability scan as a security report. +Please do not email the security list with issues on Solr dependencies or outputs from vulnerability scanning tools. Review Comment: Not 100% sure about this... I'd perhaps state explicitly that in most cases you should email solr's public lists about already-public CVEs in our dependencies. Only if they can describe how a vulnerable dependency enables a new, unknown exploit against Solr, should they report to security list. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
