Loading vulnerability…
Neo4j through version 3.4.18, when the shell server is enabled, exposes an RMI service that deserializes attacker-controlled Java objects without restriction. The setSessionVariable operation can be used to submit serialized objects. Exploitable Java deserialization gadget chains in available dependencies allow this condition to result in remote code execution.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2021-34371, targeting Neo4j version 3.4.18 when the shell-server (RMI) service is enabled and exposed. The exploit leverages JPype to interact with Java classes and requires the neo4j-shell-3.4.18.jar and ysoserial-all.jar files. The main exploit file, 'exploit.py', connects to the RMI registry (default: rmi://127.0.0.1:1337), checks for the 'shell' binding, and then attempts to exploit a deserialization vulnerability by sending a malicious payload (using the RhinoGadget) to execute an arbitrary command on the server. The README.md provides a brief description and CVE reference. The exploit is a functional proof-of-concept and requires specific configuration on the target, including the presence of the vulnerable Neo4j shell-server and the necessary Java dependencies.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.