Vulnerability-Lookup

CVE-2024-31391 (GCVE-0-2024-31391)

Vulnerability from cvelistv5 – Published: 2024-04-12 15:00 – Updated: 2025-03-13 19:45

Title

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

Summary

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

Severity ?

No CVSS data available.

CWE

CWE-532 - Insertion of Sensitive Information into Log File

Assigner

apache

References

URL

Tags

	https://lists.apache.org/thread/w7011s78lzywzwysz…	vendor-advisory
	http://www.openwall.com/lists/oss-security/2024/04/12/7

Impacted products

	Vendor	Product	Version
	Apache Software Foundation	Apache Solr Operator	Affected: 0.3.0 , ≤ 0.8.0 (semver)

Credits

Flip Hess

Show details on NVD website

JSON

To clipboard Create KEV Entry

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-31391",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-02-21T16:59:45.783042Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-03-13T19:45:50.106Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T01:52:56.571Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "vendor-advisory",
              "x_transferred"
            ],
            "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "http://www.openwall.com/lists/oss-security/2024/04/12/7"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Apache Solr Operator",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThanOrEqual": "0.8.0",
              "status": "affected",
              "version": "0.3.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Flip Hess"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator.\u003cbr\u003e\u003cbr\u003eThis issue affects all versions of the Apache Solr Operator from 0.3.0 through 0.8.0.\u003cbr\u003e\u003cbr\u003eWhen 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.\u003cbr\u003eOne common source of these operator requests is healthchecks: liveness, readiness, and startup probes are all used to determine Solr\u0027s health and ability to receive traffic.\u003cbr\u003eBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u0026nbsp;users may specifically request that authentication be required on probe endpoints as well.\u003cbr\u003eWhenever 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.\u003cbr\u003e\u003cbr\u003eWithin 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`.\u003cbr\u003e\u003cbr\u003eUsers 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.\u0026nbsp; Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\u003cbr\u003e"
            }
          ],
          "value": "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "moderate"
            },
            "type": "Textual description of severity"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-532",
              "description": "CWE-532 Insertion of Sensitive Information into Log File",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-05-01T17:09:18.226Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
        },
        {
          "url": "http://www.openwall.com/lists/oss-security/2024/04/12/7"
        }
      ],
      "source": {
        "defect": [
          "SOLR-17216"
        ],
        "discovery": "UNKNOWN"
      },
      "title": "Apache Solr Operator: Solr-Operator liveness and readiness probes may leak basic auth credentials",
      "x_generator": {
        "engine": "Vulnogram 0.1.0-dev"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2024-31391",
    "datePublished": "2024-04-12T15:00:26.569Z",
    "dateReserved": "2024-04-02T14:44:22.173Z",
    "dateUpdated": "2025-03-13T19:45:50.106Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-31391\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2024-04-12T15:15:26.157\",\"lastModified\":\"2025-06-17T20:58:50.363\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\u0027s health and ability to receive traffic.\\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\"},{\"lang\":\"es\",\"value\":\"Vulnerabilidad de inserci\u00f3n de informaci\u00f3n confidencial en un archivo de registro en el operador Apache Solr. Este problema afecta a todas las versiones del operador Apache Solr desde la 0.3.0 hasta la 0.8.0. Cuando se le solicite iniciar la seguridad de Solr, el operador habilitar\u00e1 la autenticaci\u00f3n b\u00e1sica y crear\u00e1 varias cuentas para acceder a Solr: incluidas las cuentas \\\"solr\\\" y \\\"admin\\\" para uso de los usuarios finales, y una cuenta \\\"k8s-oper\\\" que utiliza el operador. para sus propias solicitudes a Solr. Una fuente com\u00fan de estas solicitudes de operadores son las comprobaciones de estado: las sondas de actividad, preparaci\u00f3n y arranque se utilizan para determinar el estado de Solr y su capacidad para recibir tr\u00e1fico. De forma predeterminada, el operador configura las API de Solr utilizadas para estas sondas para que est\u00e9n exentas de autenticaci\u00f3n, pero los usuarios pueden solicitar espec\u00edficamente que tambi\u00e9n se requiera autenticaci\u00f3n en los endpoints de las sondas. Cada vez que una de estas sondas fallaba, si se estaba utilizando la autenticaci\u00f3n, el operador Solr crear\u00eda un \\\"evento\\\" de Kubernetes que conten\u00eda el nombre de usuario y la contrase\u00f1a de la cuenta \\\"k8s-oper\\\". Dentro del rango de versiones afectadas, esta vulnerabilidad afecta a cualquier recurso de solrcloud que (1) haya iniciado la seguridad mediante el uso de la opci\u00f3n `.solrOptions.security.authenticationType=basic` y (2) requiera que se use autenticaci\u00f3n en las sondas configurando `.solrOptions. seguridad.probesRequireAuth=true`. Se recomienda a los usuarios actualizar a Solr Operador versi\u00f3n 0.8.1, que soluciona este problema al garantizar que las sondas ya no impriman las credenciales utilizadas para las solicitudes de Solr. Los usuarios tambi\u00e9n pueden mitigar la vulnerabilidad deshabilitando la autenticaci\u00f3n en sus sondas de verificaci\u00f3n de estado usando la configuraci\u00f3n `.solrOptions.security.probesRequireAuth=false`.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-532\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:apache:solr_operator:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"0.3.0\",\"versionEndExcluding\":\"0.8.1\",\"matchCriteriaId\":\"09C3A433-6776-4F77-B921-94454D521A7E\"}]}]}],\"references\":[{\"url\":\"http://www.openwall.com/lists/oss-security/2024/04/12/7\",\"source\":\"security@apache.org\",\"tags\":[\"Mailing List\"]},{\"url\":\"https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7\",\"source\":\"security@apache.org\",\"tags\":[\"Mailing List\"]},{\"url\":\"http://www.openwall.com/lists/oss-security/2024/04/12/7\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\"]},{\"url\":\"https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\"]}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7\", \"tags\": [\"vendor-advisory\", \"x_transferred\"]}, {\"url\": \"http://www.openwall.com/lists/oss-security/2024/04/12/7\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T01:52:56.571Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 6.5, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-31391\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-02-21T16:59:45.783042Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-23T19:01:23.783Z\"}}], \"cna\": {\"title\": \"Apache Solr Operator: Solr-Operator liveness and readiness probes may leak basic auth credentials\", \"source\": {\"defect\": [\"SOLR-17216\"], \"discovery\": \"UNKNOWN\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Flip Hess\"}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"moderate\"}}}], \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Solr Operator\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.3.0\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"0.8.0\"}], \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7\", \"tags\": [\"vendor-advisory\"]}, {\"url\": \"http://www.openwall.com/lists/oss-security/2024/04/12/7\"}], \"x_generator\": {\"engine\": \"Vulnogram 0.1.0-dev\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\u0027s health and ability to receive traffic.\\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\\u00a0users 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.\\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator.\u003cbr\u003e\u003cbr\u003eThis issue affects all versions of the Apache Solr Operator from 0.3.0 through 0.8.0.\u003cbr\u003e\u003cbr\u003eWhen 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.\u003cbr\u003eOne common source of these operator requests is healthchecks: liveness, readiness, and startup probes are all used to determine Solr\u0027s health and ability to receive traffic.\u003cbr\u003eBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u0026nbsp;users may specifically request that authentication be required on probe endpoints as well.\u003cbr\u003eWhenever 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.\u003cbr\u003e\u003cbr\u003eWithin 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`.\u003cbr\u003e\u003cbr\u003eUsers 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.\u0026nbsp; Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-532\", \"description\": \"CWE-532 Insertion of Sensitive Information into Log File\"}]}], \"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2024-05-01T17:09:18.226Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-31391\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-03-13T19:45:50.106Z\", \"dateReserved\": \"2024-04-02T14:44:22.173Z\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"datePublished\": \"2024-04-12T15:00:26.569Z\", \"assignerShortName\": \"apache\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}

GSD-2024-31391

Vulnerability from gsd - Updated: 2024-04-03 05:02

Details

Aliases

CVE-2024-31391

JSON

To clipboard Create KEV Entry

{
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2024-31391"
      ],
      "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\n",
      "id": "GSD-2024-31391",
      "modified": "2024-04-03T05:02:25.528318Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security@apache.org",
        "ID": "CVE-2024-31391",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "Apache Solr Operator",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "\u003c=",
                          "version_name": "0.3.0",
                          "version_value": "0.8.0"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "Apache Software Foundation"
            }
          ]
        }
      },
      "credits": [
        {
          "lang": "en",
          "value": "Flip Hess"
        }
      ],
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\n"
          }
        ]
      },
      "generator": {
        "engine": "Vulnogram 0.1.0-dev"
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-532",
                "lang": "eng",
                "value": "CWE-532 Insertion of Sensitive Information into Log File"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7",
            "refsource": "MISC",
            "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
          }
        ]
      },
      "source": {
        "defect": [
          "SOLR-17216"
        ],
        "discovery": "UNKNOWN"
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "descriptions": [
          {
            "lang": "en",
            "value": "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.\n"
          },
          {
            "lang": "es",
            "value": "Vulnerabilidad de inserci\u00f3n de informaci\u00f3n confidencial en un archivo de registro en el operador Apache Solr. Este problema afecta a todas las versiones del operador Apache Solr desde la 0.3.0 hasta la 0.8.0. Cuando se le solicite iniciar la seguridad de Solr, el operador habilitar\u00e1 la autenticaci\u00f3n b\u00e1sica y crear\u00e1 varias cuentas para acceder a Solr: incluidas las cuentas \"solr\" y \"admin\" para uso de los usuarios finales, y una cuenta \"k8s-oper\" que utiliza el operador. para sus propias solicitudes a Solr. Una fuente com\u00fan de estas solicitudes de operadores son las comprobaciones de estado: las sondas de actividad, preparaci\u00f3n y arranque se utilizan para determinar el estado de Solr y su capacidad para recibir tr\u00e1fico. De forma predeterminada, el operador configura las API de Solr utilizadas para estas sondas para que est\u00e9n exentas de autenticaci\u00f3n, pero los usuarios pueden solicitar espec\u00edficamente que tambi\u00e9n se requiera autenticaci\u00f3n en los endpoints de las sondas. Cada vez que una de estas sondas fallaba, si se estaba utilizando la autenticaci\u00f3n, el operador Solr crear\u00eda un \"evento\" de Kubernetes que conten\u00eda el nombre de usuario y la contrase\u00f1a de la cuenta \"k8s-oper\". Dentro del rango de versiones afectadas, esta vulnerabilidad afecta a cualquier recurso de solrcloud que (1) haya iniciado la seguridad mediante el uso de la opci\u00f3n `.solrOptions.security.authenticationType=basic` y (2) requiera que se use autenticaci\u00f3n en las sondas configurando `.solrOptions. seguridad.probesRequireAuth=true`. Se recomienda a los usuarios actualizar a Solr Operador versi\u00f3n 0.8.1, que soluciona este problema al garantizar que las sondas ya no impriman las credenciales utilizadas para las solicitudes de Solr. Los usuarios tambi\u00e9n pueden mitigar la vulnerabilidad deshabilitando la autenticaci\u00f3n en sus sondas de verificaci\u00f3n de estado usando la configuraci\u00f3n `.solrOptions.security.probesRequireAuth=false`."
          }
        ],
        "id": "CVE-2024-31391",
        "lastModified": "2024-04-15T13:15:51.577",
        "metrics": {},
        "published": "2024-04-12T15:15:26.157",
        "references": [
          {
            "source": "security@apache.org",
            "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
          }
        ],
        "sourceIdentifier": "security@apache.org",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-532"
              }
            ],
            "source": "security@apache.org",
            "type": "Primary"
          }
        ]
      }
    }
  }
}

FKIE_CVE-2024-31391

Vulnerability from fkie_nvd - Published: 2024-04-12 15:15 - Updated: 2025-06-17 20:58

Severity ?

6.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Summary

References

URL	Tags
security@apache.org	http://www.openwall.com/lists/oss-security/2024/04/12/7	Mailing List
security@apache.org	https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7	Mailing List
af854a3a-2127-422b-91ae-364da2661108	http://www.openwall.com/lists/oss-security/2024/04/12/7	Mailing List
af854a3a-2127-422b-91ae-364da2661108	https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7	Mailing List

Impacted products

	Vendor	Product	Version
	apache	solr_operator	*

JSON

To clipboard Create KEV Entry

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:apache:solr_operator:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "09C3A433-6776-4F77-B921-94454D521A7E",
              "versionEndExcluding": "0.8.1",
              "versionStartIncluding": "0.3.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`."
    },
    {
      "lang": "es",
      "value": "Vulnerabilidad de inserci\u00f3n de informaci\u00f3n confidencial en un archivo de registro en el operador Apache Solr. Este problema afecta a todas las versiones del operador Apache Solr desde la 0.3.0 hasta la 0.8.0. Cuando se le solicite iniciar la seguridad de Solr, el operador habilitar\u00e1 la autenticaci\u00f3n b\u00e1sica y crear\u00e1 varias cuentas para acceder a Solr: incluidas las cuentas \"solr\" y \"admin\" para uso de los usuarios finales, y una cuenta \"k8s-oper\" que utiliza el operador. para sus propias solicitudes a Solr. Una fuente com\u00fan de estas solicitudes de operadores son las comprobaciones de estado: las sondas de actividad, preparaci\u00f3n y arranque se utilizan para determinar el estado de Solr y su capacidad para recibir tr\u00e1fico. De forma predeterminada, el operador configura las API de Solr utilizadas para estas sondas para que est\u00e9n exentas de autenticaci\u00f3n, pero los usuarios pueden solicitar espec\u00edficamente que tambi\u00e9n se requiera autenticaci\u00f3n en los endpoints de las sondas. Cada vez que una de estas sondas fallaba, si se estaba utilizando la autenticaci\u00f3n, el operador Solr crear\u00eda un \"evento\" de Kubernetes que conten\u00eda el nombre de usuario y la contrase\u00f1a de la cuenta \"k8s-oper\". Dentro del rango de versiones afectadas, esta vulnerabilidad afecta a cualquier recurso de solrcloud que (1) haya iniciado la seguridad mediante el uso de la opci\u00f3n `.solrOptions.security.authenticationType=basic` y (2) requiera que se use autenticaci\u00f3n en las sondas configurando `.solrOptions. seguridad.probesRequireAuth=true`. Se recomienda a los usuarios actualizar a Solr Operador versi\u00f3n 0.8.1, que soluciona este problema al garantizar que las sondas ya no impriman las credenciales utilizadas para las solicitudes de Solr. Los usuarios tambi\u00e9n pueden mitigar la vulnerabilidad deshabilitando la autenticaci\u00f3n en sus sondas de verificaci\u00f3n de estado usando la configuraci\u00f3n `.solrOptions.security.probesRequireAuth=false`."
    }
  ],
  "id": "CVE-2024-31391",
  "lastModified": "2025-06-17T20:58:50.363",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2024-04-12T15:15:26.157",
  "references": [
    {
      "source": "security@apache.org",
      "tags": [
        "Mailing List"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2024/04/12/7"
    },
    {
      "source": "security@apache.org",
      "tags": [
        "Mailing List"
      ],
      "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Mailing List"
      ],
      "url": "http://www.openwall.com/lists/oss-security/2024/04/12/7"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Mailing List"
      ],
      "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
    }
  ],
  "sourceIdentifier": "security@apache.org",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-532"
        }
      ],
      "source": "security@apache.org",
      "type": "Secondary"
    }
  ]
}

GHSA-G9QX-25VJ-RF53

Vulnerability from github – Published: 2024-04-12 15:37 – Updated: 2025-02-13 19:01

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.

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.

Severity ?

4.7 (Medium)


                  
                    CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

5.7 (Medium)


                  
                    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

Show details on source website

JSON

To clipboard Create KEV Entry

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/apache/solr-operator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.3.0"
            },
            {
              "fixed": "0.8.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-31391"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-532"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-04-12T21:16:19Z",
    "nvd_published_at": "2024-04-12T15:15:26Z",
    "severity": "MODERATE"
  },
  "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\u0027s health and ability to receive traffic.\nBy default, the operator configures the Solr APIs used for these probes to be exempt from authentication, but\u00a0users 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.\u00a0 Users may also mitigate the vulnerability by disabling authentication on their healthcheck probes using the setting `.solrOptions.security.probesRequireAuth=false`.",
  "id": "GHSA-g9qx-25vj-rf53",
  "modified": "2025-02-13T19:01:24Z",
  "published": "2024-04-12T15:37:22Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Apache Solr Operator liveness and readiness probes may leak basic auth credentials"
}

WID-SEC-W-2024-0881

Vulnerability from csaf_certbund - Published: 2024-04-14 22:00 - Updated: 2024-04-14 22:00

Summary

Apache Solr: Schwachstelle ermöglicht Offenlegung von Informationen

Notes

Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.

Produktbeschreibung

Apache Solr ist ein Suchmaschinen-Server für Unternehmen mit einer REST-ähnlichen API.

Angriff

Ein lokaler Angreifer kann eine Schwachstelle in Apache Solr ausnutzen, um Informationen offenzulegen.

Betroffene Betriebssysteme

- Linux - MacOS X - Windows

JSON

To clipboard Create KEV Entry

{
  "document": {
    "aggregate_severity": {
      "text": "mittel"
    },
    "category": "csaf_base",
    "csaf_version": "2.0",
    "distribution": {
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "de-DE",
    "notes": [
      {
        "category": "legal_disclaimer",
        "text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
      },
      {
        "category": "description",
        "text": "Apache Solr ist ein Suchmaschinen-Server f\u00fcr Unternehmen mit einer REST-\u00e4hnlichen API.",
        "title": "Produktbeschreibung"
      },
      {
        "category": "summary",
        "text": "Ein lokaler Angreifer kann eine Schwachstelle in Apache Solr ausnutzen, um Informationen offenzulegen.",
        "title": "Angriff"
      },
      {
        "category": "general",
        "text": "- Linux\n- MacOS X\n- Windows",
        "title": "Betroffene Betriebssysteme"
      }
    ],
    "publisher": {
      "category": "other",
      "contact_details": "csaf-provider@cert-bund.de",
      "name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
      "namespace": "https://www.bsi.bund.de"
    },
    "references": [
      {
        "category": "self",
        "summary": "WID-SEC-W-2024-0881 - CSAF Version",
        "url": "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0881.json"
      },
      {
        "category": "self",
        "summary": "WID-SEC-2024-0881 - Portal Version",
        "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0881"
      },
      {
        "category": "external",
        "summary": "Apache Mailing List vom 2024-04-14",
        "url": "https://lists.apache.org/thread/w7011s78lzywzwyszvy4d8zm99ybt8c7"
      },
      {
        "category": "external",
        "summary": "GitHub Advisory Database vom 2024-04-14",
        "url": "https://github.com/advisories/GHSA-g9qx-25vj-rf53"
      }
    ],
    "source_lang": "en-US",
    "title": "Apache Solr: Schwachstelle erm\u00f6glicht Offenlegung von Informationen",
    "tracking": {
      "current_release_date": "2024-04-14T22:00:00.000+00:00",
      "generator": {
        "date": "2024-08-15T18:07:43.816+00:00",
        "engine": {
          "name": "BSI-WID",
          "version": "1.3.5"
        }
      },
      "id": "WID-SEC-W-2024-0881",
      "initial_release_date": "2024-04-14T22:00:00.000+00:00",
      "revision_history": [
        {
          "date": "2024-04-14T22:00:00.000+00:00",
          "number": "1",
          "summary": "Initiale Fassung"
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "Operator \u003c0.8.1",
                "product": {
                  "name": "Apache Solr Operator \u003c0.8.1",
                  "product_id": "T034113"
                }
              }
            ],
            "category": "product_name",
            "name": "Solr"
          }
        ],
        "category": "vendor",
        "name": "Apache"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2024-31391",
      "notes": [
        {
          "category": "description",
          "text": "Es besteht eine Schwachstelle in Apache Solr. Dieser Fehler besteht im Modul Operator aufgrund von vertraulichen Informationen, die in Protokolldateien gespeichert werden. Ein lokaler Angreifer kann diese Schwachstelle ausnutzen, um vertrauliche Informationen offenzulegen."
        }
      ],
      "release_date": "2024-04-14T22:00:00.000+00:00",
      "title": "CVE-2024-31391"
    }
  ]
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2024-31391 (GCVE-0-2024-31391)

GSD-2024-31391

FKIE_CVE-2024-31391

GHSA-G9QX-25VJ-RF53

WID-SEC-W-2024-0881

Tags

Sightings

Nomenclature