![]() The Solr Metrics API is protected by the "metrics-read" permission. Environment variables cannot be strictly defined in Solr, like Java system properties can be, and may be set for the entire host, unlike Java system properties which are set per-Java-proccess. Users are able to specify which environment variables to hide, however, the default list is designed to work for known secret Java system properties. The Solr Metrics API publishes all unprotected environment variables available to each Apache Solr instance. * The Backup API restricts saving backups to directories that are used in the ClassLoader.Įxposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr. 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. Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue. 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. ![]() 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 backing up Solr Collections, these configSet files would be saved to disk when using the LocalFileSystemRepository (the default for backups). In the affected versions, Solr ConfigSets accepted Java jar and class files to be uploaded through the ConfigSets API. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |