Loading vulnerability…
A vulnerability in VisiWaveReport.exe, part of AZO Technologies' VisiWave Site Survey prior to version 2.1.9, allows user-assisted remote attackers to execute arbitrary code. The vulnerability is triggered when a specially crafted .vws or .vwr file with an invalid Type property is opened, leading to an untrusted pointer dereference.
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 targeting a file parsing vulnerability (CVE-2011-2386) in VisiWave Site Survey Report (VisiWaveReport.exe) for Windows. The exploit generates a malicious .VWR file that, when opened by a victim, triggers a vulnerability in the application's handling of the 'Type' property. If the property value is not recognized, the application misuses the input as a pointer, leading to code execution via a crafted ROP chain. The exploit bypasses ASLR and DEP, and allows the attacker to execute arbitrary code with the privileges of the user opening the file. The module is operational, allowing the user to select any Metasploit payload (up to 2000 bytes, avoiding certain bad characters). The exploit is local in nature, requiring user interaction (opening the malicious file). The repository is structured as a single Ruby file within the Metasploit framework, and references file paths typical for Windows installations of VisiWave and system image directories.
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.