Microsoft Windows 10 1607/10 1703/Server 2016 Hyper-V input validation

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.9$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Microsoft Windows 10 1607/10 1703/Server 2016. The impacted element is an unknown function of the component Hyper-V. This manipulation causes input validation. This vulnerability appears as CVE-2017-8623. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as critical was found in Microsoft Windows 10 1607/10 1703/Server 2016 (Operating System). Affected by this vulnerability is some unknown processing of the component Hyper-V. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect availability. The summary by CVE is:

Windows Hyper-V in Windows 10 1607, 1703, and Windows Server 2016 allows a denial of service vulnerability when it fails to properly validate input from a privileged user on a guest operating system, aka "Windows Hyper-V Denial of Service Vulnerability".

The bug was discovered 08/08/2017. The weakness was presented 08/08/2017 as KB4034674 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. This vulnerability is known as CVE-2017-8623 since 05/03/2017. The exploitation appears to be difficult. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 102264 (KB4034658: Windows 10 Version 1607 and Windows Server 2016 August 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 91405 (Microsoft Windows Security Update August 2017).

Applying the patch KB4034674 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 (102264) and SecurityFocus (BID 100042†). See VDB-102409, VDB-104989, VDB-104990 and VDB-104991 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 6.1

VulDB Base Score: 5.8
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

NVD Base Score: 6.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
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: 102264
Nessus Name: KB4034658: Windows 10 Version 1607 and Windows Server 2016 August 2017 Cumulative Update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802136
OpenVAS Name: Microsoft Windows Multiple Vulnerabilites (KB4034674)
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: KB4034674

Timelineinfo

05/03/2017 🔍
08/08/2017 +97 days 🔍
08/08/2017 +0 days 🔍
08/08/2017 +0 days 🔍
08/08/2017 +0 days 🔍
08/08/2017 +0 days 🔍
08/08/2017 +0 days 🔍
08/09/2017 +1 days 🔍
01/07/2021 +1247 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: KB4034674
Researcher: Azure Security Reliance Team.
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-8623 (🔍)
GCVE (CVE): GCVE-0-2017-8623
GCVE (VulDB): GCVE-100-105013

OVAL: 🔍

SecurityFocus: 100042 - Microsoft Windows Hyper-V CVE-2017-8623 Remote Denial of Service Vulnerability
SecurityTracker: 1039104

scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔍

Entryinfo

Created: 08/09/2017 11:46
Updated: 01/07/2021 17:16
Changes: 08/09/2017 11:46 (83), 11/04/2019 20:27 (11), 01/07/2021 17:14 (3), 01/07/2021 17:16 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!