Loading vulnerability…
Distinct Intranet Servers 3.10 and earlier contains directory traversal vulnerabilities in its TFTP Server. Remote attackers can supply dot-dot path traversal sequences in TFTP get or put commands to access files outside the intended TFTP directory, allowing arbitrary file reads or writes.
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 (modules/exploits/windows/tftp/distinct_tftp_traversal.rb) targeting a directory traversal vulnerability (CVE-2012-6664) in Distinct Intranet Servers TFTP Server version 3.10 on Windows. The exploit abuses the TFTP server's lack of path sanitization to write arbitrary files outside the intended directory, specifically to the Windows system32 and wbem\mof directories. It uploads a custom EXE payload and a MOF file, which triggers execution of the payload as SYSTEM via the Windows Management Instrumentation (WMI) service. The module is operational, allowing the attacker to execute arbitrary code on the target. The exploit requires network access to the TFTP service (default UDP port 69) and is configurable for target address and traversal depth. The only file in the repository is the Metasploit module itself, written in Ruby.
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.