Loading vulnerability…
A stack-based buffer overflow exists in the Win32AddConnection function within modules/access/smb.c in VLC media player 0.9.9 on Windows. The vulnerability is triggered when a specially crafted, overly long SMB URI is processed from a playlist file, leading to a buffer overflow condition.
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 (1 hidden).
This repository contains a single Metasploit module: 'vlc_smb_uri.rb', which exploits a stack-based buffer overflow vulnerability (CVE-2009-2484) in the Win32AddConnection function of the VideoLAN VLC media player (versions 0.9.9 through 1.0.1, Windows only). The exploit works by generating a malicious .xspf playlist file containing a specially crafted 'smb://' URI. When a user opens this file with a vulnerable VLC version, the buffer overflow is triggered, allowing execution of arbitrary code (such as a reverse shell or Meterpreter payload). The module allows the attacker to specify the payload and filename for the malicious file. The attack vector is local, requiring user interaction to open the file. The main fingerprintable endpoints are the generated .xspf file and the embedded SMB URI. The code is operational and leverages Metasploit's payload generation and file creation capabilities.
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.