WaratekVRT Sign in

Critical Org.apache.solr CVEs with a working exploit

2 CVEs, 1 protected by Waratek

Reset
More filters (1)
Columns
Vendor org.apache.solr✕
Overview 2 matches · 1 protected · 0 exploited · 0 CISA KEV
2matches 1protected50.0% 0exploited0.0% 0CISA KEV0.0%
Protected by Waratek 1 50.0% Rule in development 1 50.0% Mitigation candidate 0 0.0% No exploit published 0 0.0%
Critical 2 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 1 50.0% partly blocked 0 0.0% not blocked 1 50.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 2 100.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 1 / quarter
Rule in development: 1Protected by Waratek: 1 Critical: 2 not blocked: 1blocked by ARMR today: 1 Working exploit published: 2
Q4 171 Protected by Waratek1 Critical1 blocked by ARMR today1 Working exploit published1 Q1 180 Q2 180 Q3 180 Q4 180 Q1 190 Q2 190 Q3 190 Q4 190 Q1 200 Q2 200 Q3 200 Q4 200 Q1 210 Q2 211 Rule in development1 Critical1 not blocked1 Working exploit published1
Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21
2 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-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-2017-12629 Critical 2017-10-14 Protected by Waratek Working exploit published Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.