Loading vulnerability…
Motorola Timbuktu Pro 8.6.5 for Windows contains a stack-based buffer overflow in processing of input sent through the PlughNTCommand named pipe. A remotely supplied long malformed string can overwrite stack memory and enable 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.
This repository contains a single Metasploit module (Ruby file) that exploits a stack-based buffer overflow vulnerability in Timbuktu Pro (version 8.6.6 and earlier) on Windows. The exploit targets the 'PlughNTCommand' named pipe over SMB. The attack is performed in two stages: first, a memory leak is triggered to obtain stack addresses by abusing the nNumberOfBytesToWrite argument, and then the actual buffer overflow is performed using the leaked information to reliably execute arbitrary code. The module supports customizable Metasploit payloads (default space: 2048 bytes) and is capable of granting the attacker code execution with the privileges of the Timbuktu Pro process. The exploit requires network access to the target's SMB service and is operational, but not weaponized (payloads are customizable but not fully automated for mass exploitation). The only fingerprintable endpoint is the '\PlughNTCommand' named pipe accessed via SMB.
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.