GHSA-g9qx-25vj-rf53
- Source
- https://github.com/advisories/GHSA-g9qx-25vj-rf53
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/04/GHSA-g9qx-25vj-rf53/GHSA-g9qx-25vj-rf53.json
- Aliases
-
- CVE-2024-31391
- Published
- 2024-04-12T15:37:22Z
- Modified
- 2024-04-12T21:41:54.576546Z
- Details
-
Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator.
This issue affects all versions of the Apache Solr Operator from 0.3.0 through 0.8.0.
When asked to bootstrap Solr security, the operator will enable basic authentication and create several accounts for accessing Solr: including the "solr" and "admin" accounts for use by end-users, and a "k8s-oper" account which the operator uses for its own requests to Solr. One common source of these operator requests is healthchecks: liveness, readiness, and startup probes are all used to determine Solr's health and ability to receive traffic. By default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but users may specifically request that authentication be required on probe endpoints as well. Whenever one of these probes would fail, if authentication was in use, the Solr Operator would create a Kubernetes "event" containing the username and password of the "k8s-oper" account.
Within the affected version range, this vulnerability affects any solrcloud resource which (1) bootstrapped security through use of the
.solrOptions.security.authenticationType=basicoption, and (2) required authentication be used on probes by setting.solrOptions.security.probesRequireAuth=true.Users are recommended to upgrade to Solr Operator version 0.8.1, which fixes this issue by ensuring that probes no longer print the credentials used for Solr requests. Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting
.solrOptions.security.probesRequireAuth=false. - References