WaratekVRT Sign in
Reset
More filters (2)
Columns
Protection: None✕Vendor org.apache.solr✕
Overview 5 matches · 0 protected · 1 exploited · 0 CISA KEV · 3 public PoC · 3 EPSS ≥ 0.5
5matches 0protected0.0% 1exploited20.0% 0CISA KEV0.0% 3public PoC60.0% 3EPSS ≥ 0.560.0%
Protected by Waratek 0 0.0% Rule in development 1 20.0% Mitigation candidate 2 40.0% No exploit published 2 40.0%
Critical 5 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 5 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 20.0% Working exploit published 1 20.0% Proof of concept only 1 20.0% Forecast only 1 20.0% No public exploit 1 20.0%
split by peak 2 / quarter
No exploit published: 2Mitigation candidate: 2Rule in development: 1 Critical: 5 not blocked: 5 No public exploit: 1Forecast only: 1Proof of concept only: 1Working exploit published: 1Exploited: 1
Q4 191 Mitigation candidate1 Critical1 not blocked1 Proof of concept only1 Q1 200 Q2 200 Q3 200 Q4 201 No exploit published1 Critical1 not blocked1 Forecast only1 Q1 210 Q2 212 Rule in development1 No exploit published1 Critical2 not blocked2 Working exploit published1 No public exploit1 Q3 210 Q4 210 Q1 220 Q2 220 Q3 220 Q4 220 Q1 230 Q2 230 Q3 230 Q4 230 Q1 240 Q2 240 Q3 240 Q4 241 Mitigation candidate1 Critical1 not blocked1 Exploited1
Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24
5 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-2021-29943 Critical 2021-04-13 No exploit published No public exploit When using ConfigurableInternodeAuthHadoopPlugin for authentication, Apache Solr versions prior to 8.8.2 would forward/proxy distributed requests using server credentials instead of original client credentials. This would result in incorrect authorization resolution on the receiving hosts.
CVE-2021-27905 Critical 2021-04-13 Rule in development Working exploit published The ReplicationHandler (normally registered at "/replication" under a Solr core) in Apache Solr has a "masterUrl" (also "leaderUrl" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To prevent a SSRF vulnerability, Solr ought to check these parameters against a similar configuration it uses for the "shards" parameter. Prior to this bug getting fixed, it did not. This problem affects essentially all Solr versions prior to it getting fixed in 8.8.2.
CVE-2020-13957 Critical 2020-10-13 No exploit published Forecast only Apache Solr versions 6.6.0 to 6.6.6, 7.0.0 to 7.7.3 and 8.0.0 to 8.6.2 prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via API without authentication/authorization. The checks in place to prevent such features can be circumvented by using a combination of UPLOAD/CREATE actions.
CVE-2019-12409 Critical 2019-11-18 Mitigation candidate Proof of concept only The 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default solr.in.sh configuration file shipping with Solr. If you use the default solr.in.sh file from the affected releases, then JMX monitoring will be enabled and exposed on RMI_PORT (default=18983), without any authentication. If this port is opened for inbound traffic in your firewall, then anyone with network access to your Solr nodes will be able to access JMX, which may in turn allow them to upload malicious code for execution on the Solr server.