Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2024-31391

Опубликовано: 12 апр. 2024
Источник: redhat
CVSS3: 6.5
EPSS Низкий

Описание

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=basic option, 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.

A vulnerability was found in Apache Solr Operator. When bootstraping Solr security, a couple of initial user accounts are created by default, including a "k8s-oper" account. This account is used by the operator to send requests to Solr, such as health checks. When one of the probes used by these requests fails and authentication is being used, the Solr Operator ends, creating a Kubernetes event containing the username and password of the "k8s-oper" account.

Отчет

This vulnerability only affects solrcloud resources that use .solrOptions.security.authenticationType=basic and require authentication on probes by setting .solrOptions.security.probesRequireAuth=true

Меры по смягчению последствий

This issue can be mitigated by disabling authentication on the health check probes by setting the following configuration option: .solrOptions.security.probesRequireAuth=false

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat build of Apache Camel for Spring Boot 3solrNot affected
Red Hat Data Grid 8solrNot affected
Red Hat Fuse 7solrWill not fix
Red Hat Integration Camel K 1solrWill not fix
Red Hat JBoss Enterprise Application Platform 8solrNot affected
Red Hat JBoss Fuse Service Works 6solrOut of support scope

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-532
https://bugzilla.redhat.com/show_bug.cgi?id=2277242solr: Solr-Operator liveness and readiness probes may leak basic auth credentials

EPSS

Процентиль: 13%
0.00044
Низкий

6.5 Medium

CVSS3

Связанные уязвимости

CVSS3: 6.5
nvd
почти 2 года назад

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 "

CVSS3: 4.7
github
почти 2 года назад

Apache Solr Operator liveness and readiness probes may leak basic auth credentials

EPSS

Процентиль: 13%
0.00044
Низкий

6.5 Medium

CVSS3