Loading vulnerability…
Barracuda Spam & Virus Firewall, SSL VPN, and Web Application Firewall versions before October 2010 contain a path traversal vulnerability in the view_help.cgi endpoint. The endpoint's locale parameter does not properly sanitize user-controlled input, enabling traversal sequences and null-byte terminators to access arbitrary files on the underlying system. Unauthenticated remote attackers can retrieve sensitive files, including configuration snapshots.
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 scanner module targeting a directory traversal vulnerability (CVE-2010-20109) in multiple Barracuda products, including the Spam and Virus Firewall, SSL VPN, and Web Application Firewall. The module sends a crafted HTTP GET request to the vulnerable endpoint (/cgi-mod/view_help.cgi) with a specially constructed 'locale' parameter that performs directory traversal, allowing the attacker to read arbitrary files from the target system. By default, it attempts to retrieve the Barracuda configuration file (/mail/snapshot/config.snapshot), but the file path can be customized. The module checks the response for signs of vulnerability and outputs the file contents if successful. The exploit is operational and can be used to extract sensitive configuration or system files from affected Barracuda devices.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.