CVE-2023-50386: Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
Apache Solr could allow a remote attacker to upload arbitrary files, caused by the improper control of dynamically-managed code resources. By using Backup/Restore APIs, a remote attacker could exploit this vulnerability to upload a malicious file, which could allow the attacker to execute arbitrary code on the vulnerable system.
Other sources
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. 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.
— GitHub
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. 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.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-50386?
CVE-2023-50386 is a critical vulnerability that allows for unauthenticated file uploads in Apache Solr.
How do I fix CVE-2023-50386?
To remediate CVE-2023-50386, upgrade to Apache Solr version 9.4.1 or 8.11.3.
What software is affected by CVE-2023-50386?
CVE-2023-50386 affects Apache Solr versions from 6.0.0 up to but not including 9.4.1 and 8.11.3.
What are the potential impacts of CVE-2023-50386?
Exploitation of CVE-2023-50386 could allow a remote attacker to upload arbitrary files, potentially leading to arbitrary code execution.
When was CVE-2023-50386 disclosed?
CVE-2023-50386 was publicly disclosed on October 4, 2023.