Loading vulnerability…
A format string vulnerability exists in the logMess function of TFTP Server SP version 1.66 and earlier. Remote attackers can exploit this by sending specially crafted TFTP error packets containing format string sequences, which are improperly handled by the logMess function.
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 provides a vulnerable TFTP server implementation (opentftpd) written in C++ and a set of Python exploit scripts targeting it. The environment is containerized using Docker, with the TFTP server exposed on UDP port 5566 and random high UDP ports (60000-60100) for challenge instances. The main vulnerability exploited is a format string bug in opentftpd, which allows attackers to perform arbitrary memory writes and ultimately achieve remote code execution. The provided Python scripts (example/exp.py, 4.py, 5.py, 6.py, 7.py) demonstrate various exploitation techniques: leaking the flag file, exploiting the format string to overwrite GOT entries, and injecting shell commands via TFTP options to spawn a reverse shell. The repository is structured with Docker files for setup, the vulnerable server source, configuration files, and multiple exploit scripts. The main purpose is to demonstrate and exploit a format string vulnerability in a custom TFTP server, with operational-level payloads for file leakage and remote shell access.
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.