A stack-based buffer overflow exists in MultiMedia Soft AdjMmsEng.dll versions 7.11.1.0 and 7.11.2.7, as distributed in various MultiMedia Soft audio components for .NET. The vulnerability can be triggered by supplying an overly long string in a playlist (.pls) file, leading to a buffer overflow condition. This was originally reported in the context of Euphonics Audio Player 1.0, but may affect other products using the vulnerable DLL.
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.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (6 hidden).
This repository contains a single Metasploit module targeting a stack-based buffer overflow vulnerability in Audiotran 1.4.2.4 (CVE-2009-0476). The exploit generates a malicious .pls (playlist) file that, when opened by a victim in Audiotran, triggers a buffer overflow via a SEH overwrite, allowing arbitrary code execution. The payload is customizable and avoids specific bad characters. The attack is primarily local (user must open the file), but the module notes a potential, untested browser-based vector if the PLS extension is registered to Audiotran. The repository is structured as a typical Metasploit exploit module, written in Ruby, and leverages Metasploit's fileformat and SEH exploitation mixins. The only fingerprintable endpoint is the generated malicious file (default name: msf.pls).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/audiotran_pls.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2009-0476) in Audiotran 1.4.1 for Windows. The exploit works by generating a specially crafted .pls (playlist) file that, when opened by a victim in Audiotran, triggers the buffer overflow and executes arbitrary code. The module allows the attacker to specify a payload (up to 6000 bytes, avoiding certain bad characters) which is embedded in the malicious file. The exploit is operational and can be used to gain code execution on vulnerable systems. The attack vector is primarily local (user must open the file), but the module notes the possibility of remote exploitation if the PLS extension is registered to Audiotran and opened via a browser, though this is untested. The only fingerprintable endpoint is the malicious file itself (msf.pls). The repository is structured as a standard Metasploit exploit module and is intended for use within the Metasploit framework.
This repository contains a single Metasploit module (audio_wkstn_pls.rb) that exploits a buffer overflow vulnerability in Audio Workstation version 6.4.2.4.3 (CVE-2009-0476). The exploit works by generating a specially crafted .pls (playlist) file. When this file is opened by a user in the vulnerable Audio Workstation application on Windows, it triggers a buffer overflow, allowing the attacker to execute arbitrary code with the privileges of the user. The module allows the attacker to specify the payload, which is encoded and embedded in the malicious file. The exploit does not require network access; it is a local, file-format exploit that relies on social engineering to convince a user to open the malicious file. The only fingerprintable endpoint is the generated file (default name: msf.pls). The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to 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.