CVE-2018-0953 in the critical feed json
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripti…
published 8y ago modified 4mo ago also EUVD-2018-1733
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 66.3%
- EPSS 66.3% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 1
- Exploit-DB
Summary
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-0945, CVE-2018-0946, CVE-2018-0951, CVE-2018-0954, CVE-2018-0955, CVE-2018-1022, CVE-2018-8114, CVE-2018-8122, CVE-2018-8128, CVE-2018-8137, CVE-2018-8139.
Patch / fix
Is CVE-2018-0953 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-44694)
Exploit prediction
66.31% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44694 Microsoft Edge Chakra JIT - Magic Value Type Confusion dos, 2018-05-22
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 |
Affected products
- Microsoft Microsoft Edge
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0953
patch, vendor-advisory
-
exploit-db.com
/exploits/44694/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/103990
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1040844
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0953
- NVD CVE-2018-0953
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.