This is an automated email from the ASF dual-hosted git repository.
houston pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr-site.git
The following commit(s) were added to refs/heads/main by this push:
new f234f02d3 Add 8.11.3 CVEs
f234f02d3 is described below
commit f234f02d3101cee1a42747e8fae8c437d4c7687b
Author: Houston Putman <[email protected]>
AuthorDate: Fri Feb 9 11:13:37 2024 -0600
Add 8.11.3 CVEs
---
content/solr/security/2024-02-08-cve-2023-50291.md | 38 ++++++++++++++++++++++
content/solr/security/2024-02-08-cve-2023-50292.md | 31 ++++++++++++++++++
content/solr/security/2024-02-08-cve-2023-50298.md | 31 ++++++++++++++++++
content/solr/security/2024-02-08-cve-2023-50386.md | 34 +++++++++++++++++++
4 files changed, 134 insertions(+)
diff --git a/content/solr/security/2024-02-08-cve-2023-50291.md
b/content/solr/security/2024-02-08-cve-2023-50291.md
new file mode 100644
index 000000000..b6ccb5040
--- /dev/null
+++ b/content/solr/security/2024-02-08-cve-2023-50291.md
@@ -0,0 +1,38 @@
+Title: CVE-2023-50291: Apache Solr can leak certain passwords due to System
Property redaction logic inconsistencies
+category: solr/security
+cve: CVE-2023-50291
+
+**Severity:**
+Moderate
+
+**Versions Affected:**
+
+- Apache Solr 6.0.0 through 8.11.2
+- Apache Solr 9.0.0 before 9.3.0
+
+**Description:**
+Insufficiently Protected Credentials vulnerability in Apache Solr.
+
+This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before
9.3.0.
+One of the two endpoints that publishes the Solr process' Java system
properties, /admin/info/properties, was only setup to hide system properties
that had "password" contained in the name.
+There are a number of sensitive system properties, such as "basicauth" and
"aws.secretKey" do not contain "password", thus their values were published via
the "/admin/info/properties" endpoint.
+This endpoint populates the list of System Properties on the home screen of
the Solr Admin page, making the exposed credentials visible in the UI.
+
+This /admin/info/properties endpoint is protected under the "config-read"
permission.
+Therefore, Solr Clouds with Authorization enabled will only be vulnerable
through logged-in users that have the "config-read" permission.
+Users are recommended to upgrade to version 9.3.0 or 8.11.3, which fixes the
issue.
+A single option now controls hiding Java system property for all endpoints,
"-Dsolr.hiddenSysProps".
+By default all known sensitive properties are hidden (including
"-Dbasicauth"), as well as any property with a name containing "secret" or
"password".
+
+Users who cannot upgrade can also use the following Java system property to
fix the issue:
+`-Dsolr.redaction.system.pattern=".*(password|secret|basicauth).*"`
+
+**Mitigation:**
+Users are recommended to upgrade to version 8.11.3, 9.3.0 or later, which has
consistent systemProperty redaction logic.
+
+**Credit:**
+Michael Taggart (reporter)
+
+**References:**
+JIRA - [SOLR-16809](https://issues.apache.org/jira/browse/SOLR-16809)
+CVE - [CVE-2023-50291](https://nvd.nist.gov/vuln/detail/CVE-2023-50291)
diff --git a/content/solr/security/2024-02-08-cve-2023-50292.md
b/content/solr/security/2024-02-08-cve-2023-50292.md
new file mode 100644
index 000000000..e71095c39
--- /dev/null
+++ b/content/solr/security/2024-02-08-cve-2023-50292.md
@@ -0,0 +1,31 @@
+Title: CVE-2023-50292: Apache Solr Schema Designer blindly "trusts" all
configsets, possibly leading to RCE by unauthenticated users
+category: solr/security
+cve: CVE-2023-50292
+
+**Severity:**
+Moderate
+
+**Versions Affected:**
+
+- Apache Solr 6.0.0 through 8.11.2
+- Apache Solr 9.0.0 before 9.3.0
+
+**Description:**
+Incorrect Permission Assignment for Critical Resource, Improper Control of
Dynamically-Managed Code Resources vulnerability in Apache Solr.
+
+This issue affects Apache Solr: from 8.10.0 through 8.11.2, from 9.0.0 before
9.3.0.
+
+The Schema Designer was introduced to allow users to more easily configure and
test new Schemas and configSets.
+However, when the feature was created, the "trust" (authentication) of these
configSets was not considered.
+External library loading is only available to configSets that are "trusted"
(created by authenticated users), thus non-authenticated users are unable to
perform Remote Code Execution.
+Since the Schema Designer loaded configSets without taking their "trust" into
account, configSets that were created by unauthenticated users were allowed to
load external libraries when used in the Schema Designer.
+
+**Mitigation:**
+Users are recommended to upgrade to version 8.11.3, 9.3.0 or later.
+
+**Credit:**
+Skay (reporter)
+
+**References:**
+JIRA - [SOLR-16777](https://issues.apache.org/jira/browse/SOLR-16777)
+CVE - [CVE-2023-50292](https://nvd.nist.gov/vuln/detail/CVE-2023-50292)
diff --git a/content/solr/security/2024-02-08-cve-2023-50298.md
b/content/solr/security/2024-02-08-cve-2023-50298.md
new file mode 100644
index 000000000..7d2f03697
--- /dev/null
+++ b/content/solr/security/2024-02-08-cve-2023-50298.md
@@ -0,0 +1,31 @@
+Title: CVE-2023-50298: Apache Solr can expose ZooKeeper credentials via
Streaming Expressions
+category: solr/security
+cve: CVE-2023-50298
+
+**Severity:**
+Low
+
+**Versions Affected:**
+
+- Apache Solr 6.0.0 through 8.11.2
+- Apache Solr 9.0.0 before 9.4.1
+
+**Description:**
+Exposure of Sensitive Information to an Unauthorized Actor vulnerability in
Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from
9.0.0 before 9.4.1.
+
+Solr Streaming Expressions allows users to extract data from other Solr
Clouds, using a "zkHost" parameter.
+When original SolrCloud is setup to use ZooKeeper credentials and ACLs, they
will be sent to whatever "zkHost" the user provides.
+An attacker could setup a server to mock ZooKeeper, that accepts ZooKeeper
requests with credentials and ACLs and extracts the sensitive information,
+then send a streaming expression using the mock server's address in "zkHost".
+Streaming Expressions are exposed via the "/streaming" handler, with "read"
permissions.
+
+**Mitigation:**
+Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the
issue.
+From these versions on, only zkHost values that have the same server address
(regardless of chroot), will use the given ZooKeeper credentials and ACLs when
connecting.
+
+**Credit:**
+Qing Xu (reporter)
+
+**References:**
+JIRA - [SOLR-17098](https://issues.apache.org/jira/browse/SOLR-17098)
+CVE - [CVE-2023-50298](https://nvd.nist.gov/vuln/detail/CVE-2023-50298)
diff --git a/content/solr/security/2024-02-08-cve-2023-50386.md
b/content/solr/security/2024-02-08-cve-2023-50386.md
new file mode 100644
index 000000000..77fa4278b
--- /dev/null
+++ b/content/solr/security/2024-02-08-cve-2023-50386.md
@@ -0,0 +1,34 @@
+Title: CVE-2023-50386: Apache Solr: Backup/Restore APIs allow for deployment
of executables in malicious ConfigSets
+category: solr/security
+cve: CVE-2023-50386
+
+**Severity:**
+Moderate
+
+**Versions Affected:**
+
+- Apache Solr 6.0.0 through 8.11.2
+- Apache Solr 9.0.0 before 9.4.1
+
+**Description:**
+Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of
File with Dangerous Type, Inclusion of Functionality from Untrusted Control
Sphere vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0
through 8.11.2, from 9.0.0 before 9.4.1.
+
+In the affected versions, Solr ConfigSets accepted Java jar and class files to
be uploaded through the ConfigSets API.
+When backing up Solr Collections, these configSet files would be saved to disk
when using the LocalFileSystemRepository (the default for backups).
+If the backup was saved to a directory that Solr uses in its
ClassPath/ClassLoaders, then the jar and class files would be available to use
with any ConfigSet, trusted or untrusted.
+
+When Solr is run in a secure way (Authorization enabled), as is strongly
suggested, this vulnerability is limited to extending the Backup permissions
with the ability to add libraries.
+
+**Mitigation:**
+Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the
issue.
+In these versions, the following protections have been added:
+
+- Users are no longer able to upload files to a configSet that could be
executed via a Java ClassLoader.
+- The Backup API restricts saving backups to directories that are used in the
ClassLoader.
+
+**Credit:**
+L3yx (reporter)
+
+**References:**
+JIRA - [SOLR-16949](https://issues.apache.org/jira/browse/SOLR-16949)
+CVE - [CVE-2023-50386](https://nvd.nist.gov/vuln/detail/CVE-2023-50386)
