Deserialization of Untrusted Data
In Apache Solr before 6.6.6, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side. **EDIT** This vulnerability can also be mitigated by configuration. Disable the ConfigAPI if not in use, by running Solr with the system property “disable.configEdit=true”. Versions 7.x no longer have the Config API. 5.5.5 can be fixed by applying the patch located in the references.
CWE-502 - Deserialization of Untrusted Data
Deserialization of untrusted data vulnerabilities enable an attacker to replace or manipulate a serialized object, replacing it with malicious data. When the object is deserialized at the victim's end the malicious data is able to compromise the victim’s system. The exploit can be devastating, its impact may range from privilege escalation, broken access control, or denial of service attacks to allowing unauthorized access to the application's internal code and logic which can compromise the entire system.