Loading vulnerability…
Squirrelly v9.0.0 contains a code-injection vulnerability in handling of the component option varName. The issue is fixed in Squirrelly v9.0.1.
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.
varName component option may inject code.If you can’t patch tonight, do this now.
options.varName or related template compilation options. Restrict template configuration to hardcoded, application-controlled values. Where possible, isolate template rendering from sensitive runtime contexts and reduce process privileges to limit impact if exploitation occurs. Additional defensive measures such as input validation and code review around dynamic template compilation paths may reduce exposure until patching is completed.Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2024-40453, targeting Squirrelly v9.0.0. The exploit consists of a Python script (poc.py) and a README.md with usage instructions. The script generates a bash reverse shell payload (payload.sh), hosts it via a local HTTP server on port 80, and sends a crafted HTTP request to the victim's Squirrelly instance to trigger remote code execution. The victim downloads and executes the payload, resulting in a reverse shell connection back to the attacker's listener. The exploit requires the attacker to specify both local and remote host/port parameters. The repository is structured simply, with the main logic in poc.py and clear instructions in the README. The exploit is a functional PoC and does not include advanced features or automation beyond the described attack flow.
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.