7.6
CVE-2018-8353
- EPSS 78.91%
- Published 15.08.2018 17:29:05
- Last modified 21.11.2024 04:13:40
- Source secure@microsoft.com
- Teams watchlist Login
- Open Login
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka "Scripting Engine Memory Corruption Vulnerability." This affects Internet Explorer 9, Internet Explorer 11, Internet Explorer 10. This CVE ID is unique from CVE-2018-8355, CVE-2018-8359, CVE-2018-8371, CVE-2018-8372, CVE-2018-8373, CVE-2018-8385, CVE-2018-8389, CVE-2018-8390.
Data is provided by the National Vulnerability Database (NVD)
Microsoft ≫ Internet Explorer Version11
Microsoft ≫ Windows 10 Version-
Microsoft ≫ Windows 10 Version1607
Microsoft ≫ Windows 10 Version1703
Microsoft ≫ Windows 10 Version1709
Microsoft ≫ Windows 10 Version1803
Microsoft ≫ Windows 7 Updatesp1
Microsoft ≫ Windows 8.1
Microsoft ≫ Windows Rt 8.1
Microsoft ≫ Windows Server 2008 Versionr2 Updatesp1
Microsoft ≫ Windows Server 2012 Versionr2
Microsoft ≫ Windows Server 2016 Version-
Microsoft ≫ Windows 10 Version1607
Microsoft ≫ Windows 10 Version1703
Microsoft ≫ Windows 10 Version1709
Microsoft ≫ Windows 10 Version1803
Microsoft ≫ Windows 7 Updatesp1
Microsoft ≫ Windows 8.1
Microsoft ≫ Windows Rt 8.1
Microsoft ≫ Windows Server 2008 Versionr2 Updatesp1
Microsoft ≫ Windows Server 2012 Versionr2
Microsoft ≫ Windows Server 2016 Version-
Microsoft ≫ Internet Explorer Version10
Microsoft ≫ Internet Explorer Version9
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 78.91% | 0.99 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
nvd@nist.gov | 7.5 | 1.6 | 5.9 |
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
|
nvd@nist.gov | 7.6 | 4.9 | 10 |
AV:N/AC:H/Au:N/C:C/I:C/A:C
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.