Loading vulnerability…
Apache Solr contains a vulnerability in the interaction between the ConfigSets API, collection backup functionality, and Solr’s class loading behavior. In affected versions, ConfigSets could include uploaded Java JAR or class files. When a collection using such a ConfigSet was backed up with the default LocalFileSystemRepository, those files were written to disk. If the backup destination was a directory used by Solr’s ClassPath or ClassLoaders, the attacker-supplied classes could later be loaded and executed by Solr, including through configuration that references the implanted classes during collection creation. This creates a path from untrusted ConfigSet content to executable code loading. The issue affects Apache Solr 6.0.0 through 8.11.2 and 9.0.0 before 9.4.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/linux/http/apache_solr_backup_restore.rb) that exploits CVE-2023-50386, a remote code execution vulnerability in Apache Solr (versions 6.0.0 through 8.11.2, and 9.0.0 before 9.4.1). The exploit abuses the backup/restore API to upload a malicious Java class file to the Solr server's classpath, which is then loaded and executed, allowing arbitrary command execution as the Solr process user. The module supports authentication if required and targets the Solr HTTP API (default port 8983). The exploit is weaponized, providing customizable payloads via the Metasploit framework, and is suitable for both proof-of-concept and operational use. The main endpoints involved are the Solr HTTP interface and the server's data directory where the payload is stored and executed.
This repository provides a working exploit for CVE-2023-50386, a remote code execution vulnerability in Apache Solr's Backup/Restore APIs. The main exploit script (CVE-2023-50386.py) is a Pocsuite3 module that automates the exploitation process: it checks for authentication requirements, verifies the Solr version, uploads malicious configuration sets (conf1.zip, conf2.zip), creates and manipulates collections, and ultimately triggers the loading and execution of attacker-supplied Java code on the server. The exploit includes several Java payloads (in src/main/java/zk_backup_0/configs/conf1/) that demonstrate different techniques for bypassing Java Security Manager and JDK restrictions, including the use of JNI (with a C++ library) for native command execution. The exploit cleans up after itself by deleting the created collections and configsets. The repository is well-structured, with clear separation between the exploit logic (Python), payloads (Java), and native code (C++). It is operational and provides full remote code execution capabilities against vulnerable Solr instances.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.