CVE-2013-3111 in the critical feed json
Microsoft Internet Explorer 8 through 10 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption)…
published 13y ago modified 4mo ago also EUVD-2013-3049
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 33.5%
- EPSS 33.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Microsoft Internet Explorer 8 through 10 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3123.
Is CVE-2013-3111 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-40907)
Exploit prediction
33.54% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-40907 Microsoft Internet Explorer 9 - IEFRAME CSelectionInteractButtonBehavior::_UpdateButtonLocation Use-After-Free (MS13-047) dos, 2016-12-12
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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/40907/
exploit
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2013/ms13-047
vendor-advisory
-
us-cert.gov
/ncas/alerts/TA13-168A
third-party-advisory, us-government-resource
- blog.skylined.nl /20161212001.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16708
vdb-entry, signature
- packetstormsecurity.com /files/140124/Microsoft-Internet-Explorer-9-IEFRAME-CSelectionInteractButtonBehavior-_UpdateButtonLocation-Use
Sources
- CVE List CVE-2013-3111
- NVD CVE-2013-3111
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.