HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-993836456
It should be mentioned that the official Docker images
([_/solr](https://hub.docker.com/_/solr)) have been updated to have this fix
included by default. If you have `imageP
HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-993640127
@nosvalds from here: https://github.com/apache/solr-site/pull/55, the
consensus is that the Solr Prometheus Exporter is not actually susceptible to
this CVE
--
This is a
HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991105023
Pinning this, so that others can see the mitigation step if they come
looking for information.
--
This is an automated message from the Apache Git Service.
To respond to
HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991101468
That is the correct way to mitigate the CVE.
And you are correct, it's a good option to have by default.
--
This is an automated message from the Apache Git Service
