In Apache Solr versions 5.0.0 < 5.5.5 and 6.0.0 < 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker may take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Apache Solr running on the remote web server is affected by a remote code execution vulnerability in the Config API due to unsafe deserialization of Java objects. An unauthenticated, remote attacker can exploit this, via an HTTP POST request that points the JMX server to a malicious RMI server. An attacker could then send a crafted serialized Java object to the server, to execute arbitrary code.

According to its self-reported version number, the Oracle Primavera Unifier installation running on the remote web server is 15.x or 16.x prior to 16.2.15.9 or 17.7.x prior to 17.12.11 or 18.x prior to 18.8.11. It is, therefore, affected by multiple vulnerabilities:

  - A deserialization vulnerability exists in the Apache Solr     subcomponent of Primavera Unifier. An unauthenticated,     remote attacker can exploit this, via a specially crafted     request to the Solr Config API, to execute arbitrary code     on the target host. (CVE-2019-0192)

  - A denial of service (DoS) vulnerability exists in the Apache     Tika subcomponent of Primavera Unifier due to incorrect parsing     of a crafted sqlite file. An unauthenticated, remote attacker     can exploit this issue by convincing a user to open a     specially crafted file to cause the application to stop     responding. (CVE-2018-17197)

  - A server side request forgery exists in the Apache Solr     subcomponent of Primavera Unifier. An unauthenticated     remote attacker can exploit this issue to make Solr     perform an HTTP GET request to any reachable URL.
    (CVE-2017-3164)

  - A cross-site scripting (XSS) vulnerability exists due to     improper validation of user-supplied input before returning     it to users. An unauthenticated, remote attacker can exploit     this, by convincing a user to click a specially crafted URL,     to execute arbitrary script code in a user's browser session,     which could lead to unauthorized read, update, insert or     delete access to a subset of Primavera Unifier data.
    (CVE-2015-9251)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Apache Solr running on the remote web server is affected by a remote code execution vulnerability in the Config API due to unsafe deserialization of Java objects. An unauthenticated, remote attacker can exploit this, via an HTTP POST request that points the JMX server to a  malicious RMI server. An attacker could then send a crafted serialized Java object to the server, to execute arbitrary code.

ID	Name	Product	Family	Published	Updated	Severity
98921	Apache Solr 6.0.0 < 6.6.5 Remote Code Execution	Web App Scanning	Component Vulnerability	1/22/2020	3/14/2023	critical
98919	Apache Solr 5.0.0 < 5.5.5 Remote Code Execution	Web App Scanning	Component Vulnerability	1/22/2020	3/14/2023	critical
126447	Apache Solr 5.x <= 5.5.5 or 6.x <= 6.6.5 Deserialization Vulnerability (CVE-2019-0192)	Nessus	CGI abuses	7/3/2019	11/12/2024	critical
126829	Oracle Primavera Unifier Multiple Vulnerabilities (Jul 2019 CPU)	Nessus	CGI abuses	7/19/2019	5/9/2024	critical
123417	Apache Solr 5.x <= 5.5.5 or 6.x <= 6.6.5 Deserialization Vulnerability	Nessus	CGI abuses	3/27/2019	6/7/2024	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical