Loading vulnerability…
VideoLAN VLC media player 2.2.x contains a use-after-free vulnerability that can be triggered by a crafted MKV media file. Successful exploitation can enable arbitrary code execution; unsuccessful exploit attempts are likely to cause a denial-of-service 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.
This repository contains a single Metasploit module (vlc_mkv.rb) that exploits a use-after-free vulnerability (CVE-2018-11529) in VideoLAN VLC Media Player version 2.2.8 for Windows. The exploit works by generating two specially crafted MKV files. The victim must open the first file in VLC, with the second file present in the same directory, to trigger the vulnerability. The module supports both 32-bit and 64-bit versions of VLC 2.2.8 on Windows 10, and allows the attacker to select from a range of Metasploit payloads (such as reverse shells or command execution). The exploit is operational and can be used to achieve code execution on a vulnerable system. The main attack vector is local, requiring user interaction to open the malicious files. The only fingerprintable endpoints are the generated .mkv files themselves, which must be delivered to and opened by the target. The repository is structured as a single Ruby file compatible with the Metasploit framework, and leverages Metasploit's file format exploitation 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.