Csound versions prior to 5.16.6 contain multiple stack-based buffer overflow vulnerabilities in the getnum function, present in util/heti_main.c and util/pv_import.c. These vulnerabilities can be triggered by supplying a specially crafted hetro or PVOC file, leading to a buffer overflow on the stack.
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 (Ruby file) that exploits a stack buffer overflow vulnerability in Csound (before version 5.16.6) when importing a specially crafted hetro file. The exploit targets Windows XP SP3 and Windows 7 SP1 platforms. The module generates a malicious .csd file (default name: msf.csd) that, when imported by the vulnerable Csound application using the 'csound -U het_import' command, triggers the buffer overflow and executes arbitrary code provided by the Metasploit payload system. The exploit is operational and allows for customizable payloads, but requires user interaction to import the malicious file. No network endpoints are involved; the attack vector is local file import. The repository is structured as a standard Metasploit exploit module and is intended for use within the Metasploit framework.
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.