MongoDB versions prior to 2.0.9 and 2.2.x prior to 2.2.4 contain a vulnerability in the SpiderMonkey JavaScript engine's nativeHelper function. The function does not properly validate its input arguments, allowing remote authenticated users to supply a crafted memory address as the first argument. This can result in invalid memory access, leading to a denial of service (server crash), or potentially arbitrary 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 single Metasploit module (mongod_native_helper.rb) that exploits a remote code execution vulnerability (CVE-2013-1892) in MongoDB 2.2.3 on Linux. The exploit targets the nativeHelper feature in the SpiderMonkey JavaScript engine, which can be abused via specially crafted arguments to achieve arbitrary code execution. The module connects to the MongoDB service over TCP (default port 27017), optionally authenticates using provided credentials, and delivers a payload using a heap spray and ROP chain. The payload is customizable and can be any standard Metasploit payload (e.g., reverse shell). The exploit is operational and requires the attacker to have network access to the MongoDB instance, as well as valid credentials if authentication is enabled. The code is written in Ruby and is structured as a typical Metasploit exploit module, with options for target database, collection, username, and password.
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.