Microsoft Edge on Win10 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 on Win10. It has been declared as critical. This affects an unknown function. Such manipulation leads to memory corruption. This vulnerability is listed as CVE-2017-0221. The attack may be performed from remote. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in Microsoft Edge on Win10 (Web Browser) (version now known). It has been rated as critical. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

A vulnerability exists when Microsoft Edge improperly accesses objects in memory, aka "Microsoft Edge Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0227 and CVE-2017-0240.

The bug was discovered 05/09/2017. The weakness was presented 05/09/2017 by Liu Long with Qihoo 360 Vulcan Team as 4019472 as confirmed advisory (Website). The advisory is shared for download at portal.msrc.microsoft.com. This vulnerability is handled as CVE-2017-0221 since 09/09/2016. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/24/2020). 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 100059 (KB4019472: Windows 10 Version 1607 and Windows Server 2016 May 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 91370 (Microsoft Edge Security Update for May 2017).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (100059) and SecurityFocus (BID 98147†). See VDB-100990, VDB-100991, VDB-100992 and VDB-100994 for similar entries. Once again VulDB remains the best source for 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: 100059
Nessus Name: KB4019472: Windows 10 Version 1607 and Windows Server 2016 May 2017 Cumulative Update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 800218
OpenVAS Name: Microsoft Windows Multiple Vulnerabilities (4019472)
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: 🔍

Timelineinfo

09/09/2016 🔍
05/09/2017 +242 days 🔍
05/09/2017 +0 days 🔍
05/09/2017 +0 days 🔍
05/09/2017 +0 days 🔍
05/09/2017 +0 days 🔍
05/10/2017 +1 days 🔍
05/12/2017 +2 days 🔍
09/24/2020 +1231 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: 4019472
Researcher: Liu Long
Organization: Qihoo 360 Vulcan Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-0221 (🔍)
GCVE (CVE): GCVE-0-2017-0221
GCVE (VulDB): GCVE-100-100988

OVAL: 🔍

SecurityFocus: 98147 - Microsoft Edge CVE-2017-0221 Remote Memory Corruption Vulnerability
OSVDB: - CVE-2017-0221 - Microsoft - Edge - Memory Corruption Issue

See also: 🔍

Entryinfo

Created: 05/10/2017 10:40
Updated: 09/24/2020 22:12
Changes: 05/10/2017 10:40 (86), 09/24/2020 22:12 (8)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!