Path to dependency file: /spring-boot-project/spring-boot-starters/spring-boot-starter-data-solr/build.gradle
Path to vulnerable library: /canner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar,/canner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar
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.
CVE-2023-50386 - High Severity Vulnerability
Apache Solr Solrj
Path to dependency file: /spring-boot-project/spring-boot-starters/spring-boot-starter-data-solr/build.gradle
Path to vulnerable library: /canner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar,/canner/.gradle/caches/modules-2/files-2.1/org.apache.solr/solr-solrj/8.5.1/2b564fdae242feb34f03cfd6e470042d787c8e98/solr-solrj-8.5.1.jar
Dependency Hierarchy: - :x: **solr-solrj-8.5.1.jar** (Vulnerable Library)
Found in HEAD commit: 275c27d9dd5c88d8db426ebfb734d89d3f8e7412
Found in base branch: master
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.
Publish Date: 2024-02-09
URL: CVE-2023-50386
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-50386
Release Date: 2024-02-09
Fix Resolution: 8.11.3
Step up your Open Source Security Game with Mend here