CVE-2011-3200 is a stack-based buffer overflow in rsyslogd's parseLegacySyslogMsg function in tools/syslogd.c. rsyslog versions 4.6.x before 4.6.8 and versions 5.2.0 through 5.8.4 improperly handle an overly long TAG field in a legacy syslog message, allowing a remote attacker to terminate the rsyslogd application.
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 auxiliary module (modules/auxiliary/dos/syslog/rsyslog_long_tag.rb) that exploits an off-by-two overflow vulnerability (CVE-2011-3200) in the rsyslog daemon. The exploit works by sending a specially crafted syslog message with an excessively long tag field (512 '#' characters) over UDP to port 514 of the target. This can crash the rsyslog service, resulting in a denial of service. The module is not intended for code execution but for service disruption. The exploit targets rsyslog versions 4.6.0 to 4.6.7 and 5.8.0 to 5.8.4, primarily on Linux systems. The code is written in Ruby and is structured as a standard Metasploit auxiliary DoS module, with the main logic in the 'run' method. No hardcoded IP addresses or domains are present; the target is specified by the user.
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.