Loading vulnerability…
A stack-based buffer overflow exists in the receive_tcppacket function in net_packet.c in tinc VPN software (tincd) before 1.0.21 and 1.1 before 1.1pre7. The vulnerability is triggered by a large TCP packet sent by an authenticated peer, leading to a memcpy-based overwrite of the saved return pointer on the stack. This allows for remote code execution or denial of service (crash) on affected systems. The vulnerability is present in tinc versions 1.1-pre6 and 1.0.19, and is confirmed exploitable on Windows XP, Windows 7, and FreeBSD when compiled without modern stack protections.
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/multi/vpn/tincd_bof.rb) that exploits a post-authentication stack buffer overflow vulnerability (CVE-2013-1428) in the tincd VPN daemon. The exploit targets multiple platforms, including Windows, Linux (various distributions), FreeBSD, and ARM, with specific return addresses and offsets for each. The vulnerability allows an authenticated attacker to send a specially crafted TCP packet (default port 655) to the tincd service, resulting in arbitrary code execution. The module supports a variety of payloads, including reverse shells and custom binaries, and is weaponized for use within the Metasploit framework. The exploit is effective against tincd versions up to 1.1pre6 (and 1.0.20/1.0.19 for some platforms), but is not effective against versions compiled with certain security features (e.g., __memcpy_chk, DEP/ASLR). The repository is structured as a typical Metasploit module, with all exploit logic contained in a single Ruby file.
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.