Loading vulnerability…
CVE-2009-0182 is a buffer overflow vulnerability in VUPlayer 2.49 and earlier. The issue is triggered when VUPlayer processes a crafted .pls playlist file containing an overly long URL in a File entry, specifically noted as a long http URL in a File1 line. When the application parses this field, insufficient bounds checking can lead to memory corruption and a stack- or heap-based overflow condition, enabling arbitrary code execution in the context of the user running VUPlayer.
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/vuplayer_cue.rb) that exploits a stack-based buffer overflow vulnerability in VUPlayer version 2.49 and earlier (CVE-2009-0182). The exploit works by generating a specially crafted .cue file (default name: msf.cue) that, when opened by a user in VUPlayer, triggers a buffer overflow and allows for arbitrary code execution. The module allows the attacker to specify a payload, which is encoded and embedded in the malicious file. The exploit is local in nature, requiring social engineering or other means to convince a user to open the crafted file. The code is written in Ruby and is designed to be run within the Metasploit Framework. The repository is operational, providing a working exploit with customizable payloads.
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.