Microsoft Windows Protocol information disclosure

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.2	$0-$5k	0.00

Summaryinfo

A vulnerability was found in Microsoft Windows. It has been rated as problematic. This vulnerability affects unknown code of the component Protocol Handler. Performing a manipulation results in information disclosure. There is no exploit available. You should change the configuration settings.

Detailsinfo

A vulnerability was found in Microsoft Windows (Operating System) (version unknown). It has been classified as problematic. This affects an unknown function of the component Protocol Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.

The weakness was shared 01/01/1999. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

It is possible to mitigate the problem by applying the configuration setting .

The vulnerability is also documented in the databases at X-Force (190) and Vulnerability Center (SBV-997†). The entries VDB-88183, VDB-88182, VDB-88181 and VDB-88180 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Operating System

Vendor

Microsoft

Name

Windows

License

commercial

Website

Vendor: https://www.microsoft.com/
Product: https://www.microsoft.com/en-us/windows

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.3
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Config
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/01/1999 🔍
01/01/1999 +0 days 🔍
02/24/2003 +1515 days 🔍
06/28/2016 +4873 days 🔍
02/11/2019 +958 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Status: Not defined

GCVE (VulDB): GCVE-100-88179
X-Force: 190
Vulnerability Center: 997 - The computer has more than one protocol active, Info

See also: 🔍

Entryinfo

Created: 06/28/2016 13:04
Updated: 02/11/2019 13:33
Changes: 06/28/2016 13:04 (36), 02/11/2019 13:33 (8)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.