Loading vulnerability…
CVE-2009-20004 affects gAlan 0.2.1 for Windows, a modular audio processing environment. The vulnerability is a stack-based buffer overflow in the application's parsing of .galan project/files. According to the provided information, the application does not properly validate the length of input data while processing a .galan file. A specially crafted file can therefore overwrite stack memory, which can lead to arbitrary code execution when the file is opened.
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 module (galan_fileformat_bof.rb) that exploits a stack buffer overflow vulnerability in gAlan version 0.2.1 for Windows. The exploit works by generating a specially crafted .galan file (default name: msf.galan) that, when opened by the vulnerable application, triggers a buffer overflow and executes arbitrary code. The module allows the attacker to specify any Metasploit-supported Windows payload, making it highly flexible and weaponized. The exploit targets CVE-2009-20004 and is designed for use on Windows XP. The attack vector is local, requiring the victim to open the malicious file. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.
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.