Loading vulnerability…
CVE-2010-3275 is a buffer overflow vulnerability in the libdirectx_plugin.dll component of VideoLAN VLC Media Player versions 1.1.4 through 1.1.7. The vulnerability is triggered when VLC processes a crafted .AMV file with a malicious width value, leading to a dangling pointer condition. This flaw allows remote attackers to execute arbitrary code on the victim's system when the user opens a specially crafted .AMV file. The vulnerability was discovered by Ricardo Narvaja of Core Security Technologies and confirmed exploitable even with ASLR enabled. The issue is specific to Windows platforms and was fixed in VLC version 1.1.8.
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 (vlc_amv.rb) that exploits a dangling pointer vulnerability (CVE-2010-3275) in VLC Media Player versions 1.1.4 through 1.1.7 on Windows. The exploit is delivered via a malicious .AMV file, which is served by an HTTP server implemented in the module. When a victim visits the attacker's server using a vulnerable browser (Internet Explorer 6/7/8 on Windows XP SP3 or Vista) with the VLC ActiveX plugin, the module delivers a heap-spraying JavaScript payload and the crafted .AMV file. The exploit uses ROP chains for IE8 targets and standard shellcode for others, allowing arbitrary code execution. The module is highly weaponized, supporting customizable payloads via Metasploit, and includes logic to detect the victim's browser and serve the appropriate exploit. The only external endpoint referenced is the official VLC ActiveX control CAB file. The repository is structured as a single Ruby file, typical for Metasploit modules, and leverages both JavaScript and HTML for the browser-based attack vector.
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.