Loading vulnerability…
A vulnerability in the RPC code generator of Samba 3.x before 3.4.16, 3.5.x before 3.5.14, and 3.6.x before 3.6.4 allows remote attackers to execute arbitrary code. The flaw is due to inconsistent validation of array lengths compared to array memory allocation, which can be exploited via a crafted RPC call.
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.
This repository contains a single Metasploit module (setinfopolicy_heap.rb) that exploits a heap overflow vulnerability (CVE-2012-1182) in the LSA RPC service of the Samba daemon on Linux systems. The exploit targets specific versions of Samba (2:3.5.4, 2:3.5.8, 2:3.5.11) running on Ubuntu Server 10.10, 11.04, and 11.10. The vulnerability is triggered by sending a specially crafted SetInformationPolicy request to the Samba service over the SMB/DCERPC protocol (typically TCP port 445). The module uses brute force techniques to bypass NX protections by guessing stack pivot or ROP chain addresses, and upon success, executes arbitrary code as root. The payload is customizable and can provide a Meterpreter shell or other post-exploitation capabilities. The module is operational and requires network access to the target's SMB service. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
2 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.