Microsoft Edge Scripting Engine Object memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.7$5k-$25k0.00

Summaryinfo

A vulnerability was found in Microsoft Edge. It has been rated as critical. This affects an unknown part of the component Scripting Engine. This manipulation as part of Object causes memory corruption. This vulnerability is tracked as CVE-2017-8518. The attack is possible to be carried out remotely. No exploit exists. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Microsoft Edge (Web Browser) (version unknown). It has been declared as critical. Affected by this vulnerability is an unknown function of the component Scripting Engine. The manipulation as part of a Object leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Microsoft Edge allows a remote code execution vulnerability due to the way it accesses objects in memory, aka "Scripting Engine Memory Corruption Vulnerability".

The weakness was disclosed 08/04/2017 by Matt as KB4022714 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. This vulnerability is known as CVE-2017-8518 since 05/03/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/08/2021). The advisory points out:

A vulnerability exists when Microsoft Edge improperly accesses objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user.

The vulnerability scanner Nessus provides a plugin with the ID 100759 (KB4022714: Windows 10 Version 1511 June 2017 Cumulative Update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 91384 (Microsoft Edge Security Update for June 2017).

Applying the patch KB4022714 is able to eliminate this problem. The bugfix is ready for download at catalog.update.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (100759) and SecurityFocus (BID 100122†). The entries VDB-102373, VDB-102374, VDB-102375 and VDB-102376 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 4.2
Vendor Vector (Microsoft): 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 100759
Nessus Name: KB4022714: Windows 10 Version 1511 June 2017 Cumulative Update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802136
OpenVAS Name: Microsoft Windows Multiple Vulnerabilites (KB4022727)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: KB4022714

Timelineinfo

05/03/2017 🔍
06/13/2017 +41 days 🔍
08/01/2017 +49 days 🔍
08/04/2017 +3 days 🔍
08/04/2017 +0 days 🔍
08/10/2017 +6 days 🔍
08/11/2017 +1 days 🔍
01/08/2021 +1246 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: KB4022714
Researcher: Matt Miller (Matt)
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-8518 (🔍)
GCVE (CVE): GCVE-0-2017-8518
GCVE (VulDB): GCVE-100-105217

OVAL: 🔍

SecurityFocus: 100122 - Microsoft Edge CVE-2017-8518 Scripting Engine Remote Memory Corruption Vulnerability

See also: 🔍

Entryinfo

Created: 08/11/2017 04:05
Updated: 01/08/2021 18:37
Changes: 08/11/2017 04:05 (90), 11/06/2019 10:57 (4), 01/08/2021 18:37 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!