CVE-2015-6168 in the critical feed json
Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, a…
published 10y ago modified 4mo ago also EUVD-2015-6111
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.7%
- EPSS 30.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Microsoft Edge Memory Corruption Vulnerability," a different vulnerability than CVE-2015-6153.
Is CVE-2015-6168 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-40878)
Exploit prediction
30.73% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-40878 Microsoft Edge - CMarkup::EnsureDeleteCFState Use-After-Free (MS15-125) dos, 2016-12-06
- blog.skylined.nl http://blog.skylined.nl/20161201001.html 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/40878/
exploit, third-party-advisory, vdb-entry
-
blog.skylined.nl
/20161201001.html
exploit, third-party-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2015/ms15-125
vendor-advisory
-
securitytracker.com
/id/1034316
vdb-entry
-
zerodayinitiative.com
/advisories/ZDI-15-583
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2016/Dec/4
mailing-list, third-party-advisory
Sources
- CVE List CVE-2015-6168
- NVD CVE-2015-6168
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.