1
Candidate: CVE-2017-7660
4
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7660
5
https://issues.apache.org/jira/browse/SOLR-10624
6
http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/2f5ecbcf
7
http://mail-archives.us.apache.org/mod_mbox/www-announce/201707.mbox/%3CCAOOKt53EgrybaD%2BiSn-nBbvFdse-szhg%3DhMoDZuvUvyMme-Z%3Dg%40mail.gmail.com%3E
9
Apache Solr uses a PKI based mechanism to secure inter-node communication
10
when security is enabled. It is possible to create a specially crafted node
11
name that does not exist as part of the cluster and point it to a malicious
12
node. This can trick the nodes in cluster to believe that the malicious
13
node is a member of the cluster. So, if Solr users have enabled BasicAuth
14
authentication mechanism using the BasicAuthPlugin or if the user has
15
implemented a custom Authentication plugin, which does not implement either
16
"HttpClientInterceptorPlugin" or "HttpClientBuilderPlugin", his/her servers
17
are vulnerable to this attack. Users who only use SSL without basic
18
authentication or those who use Kerberos are not affected.
21
sbeattie> introduced in solr 5.3
28
upstream_lucene-solr: needs-triage
29
precise/esm_lucene-solr: DNE
30
trusty_lucene-solr: not-affected (code not present)
31
vivid/ubuntu-core_lucene-solr: DNE
32
xenial_lucene-solr: not-affected (code not present)
33
yakkety_lucene-solr: not-affected (code not present)
34
zesty_lucene-solr: not-affected (code not present)
35
devel_lucene-solr: not-affected (code not present)