WaratekVRT Sign in

Exploited Org.apache.solr CVEs

6 CVEs, 4 protected by Waratek

Reset
More filters (1)
Columns
Vendor org.apache.solr✕
Overview 6 matches · 3 protected · 2 CISA KEV · 5 public PoC
6matches 3protected50.0% 2CISA KEV33.3% 5public PoC83.3%
Protected by Waratek 4 66.7% Rule in development 0 0.0% Mitigation candidate 2 33.3% No exploit published 0 0.0%
Critical 2 33.3% High 3 50.0% Medium 1 16.7% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 50.0% partly blocked 1 16.7% not blocked 2 33.3% not established 0 0.0% unrecorded 0 0.0%
Exploited 6 100.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 3 / year
Mitigation candidate: 2Protected by Waratek: 4 Medium: 1High: 3Critical: 2 not blocked: 2partly blocked: 1blocked by ARMR today: 3 Exploited: 6
20131 Protected by Waratek1 Medium1 blocked by ARMR today1 Exploited1 20140 20150 20160 20170 20180 20193 Protected by Waratek3 Critical1 High2 blocked by ARMR today2 partly blocked1 Exploited3 20200 20210 20220 20230 20242 Mitigation candidate2 Critical1 High1 not blocked2 Exploited2
201320142015201620172018201920202021202220232024
6 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-45216 Critical 2024-10-16 Mitigation candidate Exploited Improper Authentication vulnerability in Apache Solr. Solr instances using the PKIAuthenticationPlugin, which is enabled by default when Solr Authentication is used, are vulnerable to Authentication bypass. A fake ending at the end of any Solr API URL path, will allow requests to skip Authentication while maintaining the API contract with the original URL Path. This fake ending looks like an unprotected API path, however it is stripped off internally after authentication but before API routing. This issue affects Apache Solr: from 5.3.0 before 8.11.4, from 9.0.0 before 9.7.0. Users are recommended to upgrade to version 9.7.0, or 8.11.4, which fix the issue.
CVE-2023-50386 High 2024-02-09 Mitigation candidate Exploited 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-2019-17558 High 2019-12-30 Protected by Waratek Exploited Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset `velocity/` directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting `params.resource.loader.enabled` by defining a response writer with that setting set to `true`. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is `trusted` (has been uploaded by an authenticated user).
CVE-2019-0193 High 2019-08-01 Protected by Waratek Exploited In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property "enable.dih.dataConfigParam" to true.
CVE-2019-0192 Critical 2019-03-07 Protected by Waratek Exploited In Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.
CVE-2013-6397 Medium 2013-12-07 Protected by Waratek Exploited Directory traversal vulnerability in SolrResourceLoader in Apache Solr before 4.6 allows remote attackers to read arbitrary files via a .. (dot dot) or full pathname in the tr parameter to solr/select/, when the response writer (wt parameter) is set to XSLT. NOTE: this can be leveraged using a separate XXE (XML eXternal Entity) vulnerability to allow access to files across restricted network boundaries.