Server Side Request Forgery in Apache Solr
Summary
CVE-2017-3164: Server Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (inclusive). Affects lucene-solr versions >= 6de56f9cbd200a23df974e7bcc2957c4526d7283, <= 719cde97f84640faa1e3525690d262946571245f. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Solr is an open-source search platform built on Apache Lucene. It provides full-text search, faceted search, and indexing capabilities. Solr is widely used in various applications and is known for its scalability and performance. However, versions 1.3 until 7.6 (inclusive) of Solr are vulnerable to Server Side Request Forgery (SSRF).
Vulnerability Detail
The SSRF vulnerability in Solr arises from the lack of a whitelist mechanism for the 'shards' parameter. This allows a remote attacker with access to the server to make Solr perform an HTTP GET request to any reachable URL. By exploiting this vulnerability, an attacker can potentially access internal resources, bypass security controls, or perform other malicious actions.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
Currently, there is no known workaround for this vulnerability. It is essential to apply the official patches or updates provided by the Apache Solr project to mitigate the risk.
Conclusion
The Server Side Request Forgery (SSRF) vulnerability in Apache Solr can have serious security implications. It is crucial to promptly update to a non-vulnerable version of Solr and follow the recommended security practices. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for lucene-solr →
FAQ
Server Side Request Forgery (SSRF) is a vulnerability that allows an attacker to make requests from the server to other internal or external resources. It can be used to bypass security controls, access sensitive information, or perform actions on behalf of the server.
The impact of this vulnerability depends on the specific configuration and permissions of the Solr server. In some cases, it can lead to unauthorized access to internal resources, data leakage, or further exploitation of other vulnerabilities.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Solr installation is affected by this vulnerability. It analyzes your manifest file (e.g., package-lock.json) and provides real-time alerts for open-source vulnerabilities.
At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is crucial to apply the necessary patches and updates to prevent potential exploitation.
You can find more information about this vulnerability, including technical details and mitigation steps, in the official CVE-2017-3164 report (https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2017-3164.json).
References
Related vulnerabilities
Recent vulnerabilities recorded for lucene-solr.
