Apache Solr Remote Code Execution Vulnerability Due to Default Configuration (CVE-2019-12409)

Apache has released a an******@ap****.org/msg05559.html” target=”_blank” rel=”noopener noreferrer”>security update to fix a remote code execution vulnerability in Solr, tracked as CVE-2019-12409. The flaw arises due to a default insecure parameter in the solr.in.sh configuration file, which was shipped with affected Solr versions.


CVE-2019-12409 was first reported in July 2019. A week ago, security researcher demonstrated that the flaw could be exploited to achieve remote code execution. A proof-of-concept to exploit this vulnerability was released on GitHub.

The flaw exists because the ENABLE_REMOTE_JMX_OPTS option is set to true by default in the ‘solr.in.sh‘ configuration file, which can be exploited to execute arbitrary code on the targeted system. If any user uses the default ‘solr.in.sh‘ file in affected systems, then Java Management Extensions (JMX) monitoring will be enabled and exposed on RMI_PORT (default=18983) without any authentication.

Vulnerable configuration from ‘solr.in.sh’ file

This could allow remote attackers to reach RMI port and leverage the vulnerability to upload malicious code to the server and then execute arbitrary code on the machine.

After Successful Exploitation

Affected Products:

Apache Solr 8.1.1 and 8.2.0 (Linux version)
Windows operating systems are not affected.


Apache Solr released updated versions 8.3.0 to fix this vulnerability. As a workaround, users are advised to set ENABLE_REMOTE_JMX_OPTS parameter to ‘false’ in solr.in.sh file.

Qualys customers can scan their network with QID:13623 to detect vulnerable assets remotely. Kindly continue to follow on Qualys Threat Protection for more coverage on vulnerabilities.

References & Sources:

an******@ap****.org/msg05559.html” target=”_blank” rel=”noopener noreferrer”>https://www.mail-archive.com/an******@ap****.org/msg05559.html




Leave a Reply

Your email address will not be published. Required fields are marked *