S4E just found a high top 10 tcp port service scan
critical·Product Based Web Vulnerabilities·Updated Dec 16, 2023

CVE-2021-27905 Scanner

Detects 'Server-Side-Request-Forgery (SSRF)' vulnerability in Apache Solr affects v. before 8.8.2.

Est. Time~15 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.9k
Times Used
continuous scan runs
3.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2021-27905
9.8
CVSS

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.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
Apache Solrby Apache Software Foundation
AFFECTED< 8.8.2SAFE ✓≥ 8.8.2
Updated Aug 21, 2026View on NVD →
Detail

Apache Solr is a widely used open-source search engine platform used by many organizations to manage their data. It is a popular choice because of its ability to handle high volumes of data and its fast speed in performing searches, making it an ideal tool for businesses with large amounts of data. Solr is normally registered at "/replication" under a Solr core, and it uses ReplicationHandler to replicate index data into the local core. 

Recently, a vulnerability, CVE-2021-27905, was detected in Apache Solr. This vulnerability affected essentially all Solr versions prior to its fix in version 8.8.2. The ReplicationHandler in Solr has a "masterUrl" parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data. To prevent a SSRF (Server-Side Request Forgery) vulnerability, Solr ought to check these parameters against a similar configuration it uses for the "shards" parameter. However, prior to the fix, it did not, making it extremely vulnerable to attacks.

Exploitation of this vulnerability can lead to attacks on the core, allowing attackers to execute arbitrary code in the context of the Solr instance. Attackers could also use the vulnerability to bypass firewalls and other security measures to gain access to sensitive data. In addition, attackers could use this vulnerability to launch other attacks, such as Distributed Denial of Service (DDoS) attacks.

Thanks to the pro features of the s4e.io platform, you can easily and quickly learn about vulnerabilities in your digital assets. By using this platform, you can stay ahead of potential vulnerabilities and threats, ensuring the integrity and security of your data. Don't wait until it's too late - sign up now and protect yourself against potential attacks by staying informed about the latest security threats and vulnerabilities.

 

REFERENCES

Solution Advice

To protect against this vulnerability, you can take the following precautions:

  • Update to the latest version of Apache Solr.
  • Monitor your logs and network activity for suspicious activity or requests.
  • Use a web application firewall to prevent attacks.
  • Implement strict input validation and parameter filtering to prevent SSRF attacks.
  • Train your employees on how to identify and report potential security threats.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

CVE-2021-27905 scanner - Server-Side-Request-Forgery (SSRF) vulnerability in Apache Solr S4E