CVE-2016-3321 json
Microsoft Internet Explorer 10 and 11 load different files for attempts to open a file:// URL depending on whether the file exists, which a…
published 2016-08-09 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-4353
- cvss
- 2.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 37.9%
- EPSS 37.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Metasploit
Summary
Microsoft Internet Explorer 10 and 11 load different files for attempts to open a file:// URL depending on whether the file exists, which allows local users to enumerate files via vectors involving a file:// URL and an HTML5 sandbox iframe, aka "Internet Explorer Information Disclosure Vulnerability."
Timeline
- First public exploit (Metasploit auxiliary/gather/ie_sandbox_findfiles)
- Published
Exploit prediction
37.95% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/gather/ie_sandbox_findfiles Internet Explorer Iframe Sandbox File Name Disclosure Vulnerability metasploit auxiliary, normal rank, 2016-08-09
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 2.5 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2016/ms16-095
vendor-advisory
-
securitytracker.com
/id/1036562
vdb-entry
-
securify.nl
/advisory/SFY20160301/internet_explorer_iframe_sandbox_local_file_name_disclosure_vulnerability.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2016/Aug/44
mailing-list, third-party-advisory
-
securityfocus.com
/archive/1/539174/100/0/threaded
mailing-list
-
securityfocus.com
/bid/92291
vdb-entry
Sources
- CVE List CVE-2016-3321
- NVD CVE-2016-3321
Fencer Vulns 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.