Loading vulnerability…
ABBS Software Audio Media Player version 3.1 is affected by a stack-based buffer overflow vulnerability. The provided information identifies the issue as CWE-121 but does not include the specific vulnerable function, code path, attack vector, or triggering input. In general, this class of flaw occurs when data written to a stack-allocated buffer exceeds its bounds, potentially corrupting adjacent stack memory and altering control flow.
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 (abbs_amp_lst.rb) that exploits a buffer overflow vulnerability (CVE-2019-5621) in ABBS Audio Media Player 3.1 on Windows XP SP3 and Windows 7 SP1. The exploit works by generating a specially crafted .lst playlist file that, when opened by the vulnerable application, triggers a buffer overflow and executes arbitrary code with the privileges of the user. The module allows the attacker to select a Metasploit payload, which is embedded in the malicious file. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only fingerprintable endpoint is the crafted .lst file, which must be delivered to and opened by the target user. The repository is structured as a single Ruby file following Metasploit conventions, with all exploit logic contained within the file.
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.