CVE-2011-2386 in the critical feed json
VisiWaveReport.exe in AZO Technologies, Inc.
published 2011-06-08 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2375
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 45.2%
- EPSS 45.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
VisiWaveReport.exe in AZO Technologies, Inc. VisiWave Site Survey before 2.1.9 allows user-assisted remote attackers to execute arbitrary code via a (1) vws and (2) vwr file with an invalid Type property, which triggers an untrusted pointer dereference.
Timeline
- First public exploit (Metasploit exploit/windows/fileformat/visiwave_vwr_type)
- Published
Exploit prediction
45.22% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/visiwave_vwr_type VisiWave VWR File Parsing Vulnerability metasploit exploit, great rank, 2011-05-20
- EDB-17317 VisiWave - '.VWR' File Parsing Trusted Pointer (Metasploit) local, 2011-05-23
- stratsec.net http://www.stratsec.net/Research/Advisories/VisiWave-Site-Survey-Report-Trusted-Pointer-%28SS-20 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/47948 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/17317
exploit
-
stratsec.net
/Research/Advisories/VisiWave-Site-Survey-Report-Trusted-Pointer-%28SS-20
exploit
-
securityfocus.com
/bid/47948
vdb-entry, exploit
-
secunia.com
/advisories/44636
third-party-advisory, vendor-advisory
-
visiwave.com
/blog/index.php?/archives/4-Version-2.1.9-Released.html
vendor-advisory
-
osvdb.org
/72464
vdb-entry
Sources
- CVE List CVE-2011-2386
- NVD CVE-2011-2386
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.