Approved changes feed: RSS · Atom

cpe:2.3:a:apache:solr:6.2.0:*:*:*:*:*:*:*

part: a version: 6.2.0 update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductSolr (e541f611-5f4f-518b-9c5a-edac6afba2d9)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/solr purl2cpe 2026-06-01 10:14:26.416472
pkg:github/apache/solr purl2cpe 2026-06-01 10:14:26.416473
pkg:maven/org.apache.solr/solr purl2cpe 2026-06-01 10:14:26.416475
pkg:maven/org.apache.solr/solrj purl2cpe 2026-06-01 10:14:26.416476
pkg:rpm/opensuse/solr purl2cpe 2026-06-01 10:14:26.416478
pkg:sourceforge/apache-solr purl2cpe 2026-06-01 10:14:26.416479

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2017-9803 vulnerable 2026-06-08 05:10:10.638091 Details available
Apache Solr's Kerberos plugin can be configured to use delegation tokens, which allows an application to reuse the authentication of an end-user or another application. There are two issues with this functionality (when using SecurityAwareZkACLProvider type of ACL provider e.g. SaslZkACLProvider). Firstly, access to the security configuration can be leaked to users other than the solr super user. Secondly, malicious users can exploit this leaked configuration for privilege escalation to further expose/modify private data and/or disrupt operations in the Solr cluster. The vulnerability is fixed from Apache Solr 6.6.1 onwards.
Published: 2017-09-18T21:00:00.000Z
Updated: 2024-09-17T02:01:07.460Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-7660 vulnerable 2026-06-08 05:10:05.712773 Details available
Apache Solr uses a PKI based mechanism to secure inter-node communication when security is enabled. It is possible to create a specially crafted node name that does not exist as part of the cluster and point it to a malicious node. This can trick the nodes in cluster to believe that the malicious node is a member of the cluster. So, if Solr users have enabled BasicAuth authentication mechanism using the BasicAuthPlugin or if the user has implemented a custom Authentication plugin, which does not implement either "HttpClientInterceptorPlugin" or "HttpClientBuilderPlugin", his/her servers are vulnerable to this attack. Users who only use SSL without basic authentication or those who use Kerberos are not affected.
Published: 2017-07-07T19:00:00.000Z
Updated: 2024-09-16T18:13:03.269Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-3163 vulnerable 2026-06-08 05:09:26.706256 Details available
When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.
Published: 2017-08-30T14:00:00.000Z
Updated: 2024-09-16T18:39:30.795Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.