Loading vulnerability…
A buffer overflow vulnerability exists in the report function of xtacacsd versions 4.1.2 and earlier. The vulnerability can be triggered by sending a specially crafted CONNECT TACACS command, which causes the report function to overflow a buffer, potentially allowing remote attackers to execute arbitrary code on the affected system.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/freebsd/tacacs/xtacacsd_report.rb) that exploits a stack buffer overflow vulnerability in XTACACSD versions 4.1.2 and earlier, running on FreeBSD 6.2-Release. The exploit works by sending a specially crafted XTACACS UDP packet to port 49, with an overly long username field, triggering the overflow and allowing arbitrary code execution. The module supports brute-forcing the return address within a specified range, increasing the likelihood of successful exploitation. The payload is customizable and leverages Metasploit's payload framework, allowing the attacker to execute arbitrary code (typically a shell) on the target system. The exploit requires network access to the target's UDP port 49. The repository is structured as a standard Metasploit exploit module, written in Ruby, and is operational with a working payload mechanism.
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.