Loading vulnerability…
Varnish reverse proxy server versions prior to 2.1.0 expose a Command Line Interface (CLI) in the master process that does not require authentication for commands received over a TCP port. This allows remote attackers to execute arbitrary code via the vcl.inline directive (by supplying VCL with inline C code), change the ownership of the master process using param.set, stop, and start directives, read the initial line of arbitrary files via vcl.load, and perform CSRF attacks by leveraging a victim's network position and lack of input validation in directives.
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 (2 hidden).
This repository contains a single Metasploit auxiliary scanner module targeting Varnish Cache's CLI interface (default TCP port 6082). The module exploits CVE-2009-2936 by abusing the vcl.load command to trigger an error message that leaks the first line of an arbitrary file on the target system. The module can optionally authenticate to the CLI if a password is provided, but will also attempt unauthenticated access. The default file targeted is /etc/passwd, but this can be changed by the user. The exploit is a proof-of-concept and does not provide a full shell or arbitrary code execution, but demonstrates the ability to read sensitive files via network access to the Varnish CLI. The code is written in Ruby and is structured as a standard Metasploit module.
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.