Microsoft Windows up to Server 2016 Input Method Editor data processing

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

Summaryinfo

A vulnerability identified as critical has been detected in Microsoft Windows up to Server 2016. This vulnerability affects unknown code of the component Input Method Editor. Performing a manipulation results in data processing. This vulnerability is cataloged as CVE-2017-8591. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Microsoft Windows up to Server 2016 (Operating System). It has been classified as very critical. This affects some unknown functionality of the component Input Method Editor. The manipulation with an unknown input leads to a data processing vulnerability. CWE is classifying the issue as CWE-19. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Windows Input Method Editor (IME) in Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an remote code execution vulnerability when it fails to properly handle objects in memory, aka "Windows IME Remote Code Execution Vulnerability".

The bug was discovered 08/08/2017. The weakness was shared 08/08/2017 with Microsoft as KB4034674 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2017-8591 since 05/03/2017. It is possible to initiate the attack remotely. A authentication is required for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/07/2021).

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 99430†). The entries VDB-102409, VDB-104989, VDB-104990 and VDB-104991 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.7

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Data processing
CWE: CWE-19
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
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 (KB4034681)
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 +0 days 🔍
01/07/2021 +1247 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: KB4034674
Researcher: Microsoft
Organization: Microsoft
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-8591 (🔍)
GCVE (CVE): GCVE-0-2017-8591
GCVE (VulDB): GCVE-100-105009

OVAL: 🔍

SecurityFocus: 99430 - Microsoft Windows CVE-2017-8591 Remote Code Execution Vulnerability
SecurityTracker: 1039097

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

Entryinfo

Created: 08/09/2017 11:33
Updated: 01/07/2021 16:42
Changes: 08/09/2017 11:33 (90), 06/06/2020 08:37 (6), 01/07/2021 16:39 (2), 01/07/2021 16:42 (1)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!