CVE-2017-7660
7.5 · HIGHOverview
CVE-2017-7660 is a high-severity vulnerability affecting apache solr. It was published on July 7, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).
This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
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.
Remediation
Check the references section for vendor advisories and patches from apache. Update solr to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2017-7660?
CVE-2017-7660 is a high-severity vulnerability affecting apache solr. It was published on July 7, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).
How severe is CVE-2017-7660?
This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2017-7660?
Check the references section for vendor advisories and patches from apache. Update solr to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2017-7660?
CyberStrike's AI-powered security agents can automatically detect CVE-2017-7660 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related HIGH CVEs from 2017
View all →An issue was discovered in St. Jude Medical Merlin@home, versions prior to Version 8.2.2 (RF models:
Unrestricted file upload vulnerability in the fileUnzip->unzip method in Dotclear before 2.10.3 allo
The Parental Control panel in Genexis devices with DRGOS before 1.14.1 allows remote authenticated u
An issue was discovered in EMC ScaleIO versions before 2.0.1.1. A low-privileged local attacker may
eClinicalWorks Population Health (CCMR) suffers from an SQL injection vulnerability in portalUserSer
eClinicalWorks Population Health (CCMR) suffers from a cross-site request forgery (CSRF) vulnerabili
Microsoft Edge allows remote attackers to bypass the Same Origin Policy via vectors involving the ab
Adobe Flash Player versions 24.0.0.186 and earlier have an exploitable memory corruption vulnerabili
Adobe Flash Player versions 24.0.0.186 and earlier have an exploitable memory corruption vulnerabili
Adobe Flash Player versions 24.0.0.186 and earlier have an exploitable heap overflow vulnerability w
Adobe Flash Player versions 24.0.0.186 and earlier have an exploitable memory corruption vulnerabili
Adobe Flash Player versions 24.0.0.186 and earlier have an exploitable memory corruption vulnerabili