CVE-2024-31391: Github.com/apache/solr operator Apache Solr Operator Liveness And Vulnerability

MODERATE
Advisory Identifier: GHSA-g9qx-25vj-rf53
CVSS 4.7
CWE-532
Published
Advisory Summary

CVE-2024-31391 is a MODERATE (CVSS 4.7) apache solr operator liveness and vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Github.com/apache/solr operator libraries in the Go ecosystem. The issue involves apache solr operator liveness and readiness probes may leak basic auth credentials. Remediation is available by upgrading affected packages to version 0.8.1.

CVE-2024-31391 at a Glance

CVE Identifier CVE-2024-31391
GHSA Identifier GHSA-g9qx-25vj-rf53
Severity MODERATE
CVSS v3.1 Base Score 4.7
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Github.com/apache/solr operator
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-31391

To remediate this vulnerability, upgrade all affected Github.com/apache/solr operator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/apache/solr-operator fixed: 0.8.1
Upgrade github.com/apache/solr-operator to 0.8.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/apache/solr-operator

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-31391, inspect your project dependencies for Github.com/apache/solr operator:

inspect dependencies for github.com/apache/solr-operator

Analyze the terminal output to locate any version of Github.com/apache/solr operator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Github.com/apache/solr operator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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`.

CVE-2024-31391 Affected Github.com/apache/solr operator Versions

1 component(s)
Fixed Versions:
0.8.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/apache/solr-operator
Go
≥ 0.3.0
< 0.8.1
0.8.1

References

Frequently Asked Questions

What is CVE-2024-31391?
CVE-2024-31391 is a security vulnerability in Github.com/apache/solr operator involving Apache Solr Operator liveness and readiness probes may leak basic auth credentials under CWE-532: Insertion of Sensitive Information into Log File.
Which Github.com/apache/solr operator versions are affected?
Affected versions include releases prior to 0.8.1 across affected packages: github.com/apache/solr-operator.
What version fixes CVE-2024-31391?
Upgrading to 0.8.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/apache/solr-operator affected?
Yes, github.com/apache/solr-operator is affected in releases prior to 0.8.1. Upgrade your dependency to 0.8.1 or later.
What is the CVSS score of CVE-2024-31391?
CVE-2024-31391 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2024-31391?
CVE-2024-31391 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Go dependencies for CVE-2024-31391?
Run the dependency tree command: 'inspect dependencies for github.com/apache/solr-operator'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g9qx-25vj-rf53",
  "modified" : "2025-02-13T19:01:24Z",
  "published" : "2024-04-12T15:37:22Z",
  "aliases" : [ "CVE-2024-31391" ],
  "summary" : "Apache Solr Operator liveness and readiness probes may leak basic auth credentials",
  "details" : "Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator.\n\nThis issue affects all versions of the Apache Solr Operator from 0.3.0 through 0.8.0.\n\nWhen 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.\nOne 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.\nBy 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.\nWhenever 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.\n\nWithin 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`.\n\nUsers 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`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/apache/solr-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.3.0"
      }, {
        "fixed" : "0.8.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-31391"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apache/solr-operator"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2024/04/12/7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-04-12T21:16:19Z",
    "nvd_published_at" : "2024-04-12T15:15:26Z"
  }
}