CVE-2017-11839 in the critical feed json
Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to take…
published 2017-11-15 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3439
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 62.4%
- EPSS 62.4% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 1
- Exploit-DB
Summary
Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to take control of an affected system, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11836, CVE-2017-11837, CVE-2017-11838, CVE-2017-11840, CVE-2017-11841, CVE-2017-11843, CVE-2017-11846, CVE-2017-11858, CVE-2017-11859, CVE-2017-11861, CVE-2017-11862, CVE-2017-11866, CVE-2017-11869, CVE-2017-11870, CVE-2017-11871, and CVE-2017-11873.
Patch / fix
Timeline
- Published
- First public exploit (EDB-43180)
Exploit prediction
62.36% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-43180 Microsoft Edge Chakra JIT - 'BailOutOnTaggedValue' Bailouts Type Confusion dos, 2017-11-27
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-11839
patch, vendor-advisory
-
exploit-db.com
/exploits/43180/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1039780
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/101735
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-11839
- NVD CVE-2017-11839
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.