Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets

Summary

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.

Timeline

1. Feb 9, 2024, 5:28 PM UTCCVE published
2. Apr 30, 2024, 4:00 AM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Apr 24, 2025, 3:47 PM UTCRecord last updated
4. Oct 28, 2026EPSS reached 10%

   FIRST estimates at least a 10% chance of exploitation in the next 30 days

Affected versions

• Apache Software Foundation Apache Solr

  From 6.0.0 · through 8.11.2; From 9.0.0 · fixed in 9.4.1

• org.apache.solr:solr-coreMaven

  From 6.0.0 · fixed in 8.11.3

• org.apache.solr:solr-coreMaven

  From 9.0.0 · fixed in 9.4.1

References 4