Microsoft Windows NT 4.0 SP4/NT 4.0 SP5 Performance Counter memory leak

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

Summaryinfo

A vulnerability identified as problematic has been detected in Microsoft Windows NT 4.0 SP4/NT 4.0 SP5. This affects an unknown part of the component Performance Counter. Performing a manipulation results in memory leak. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Microsoft Windows NT 4.0 SP4/NT 4.0 SP5 (Operating System). It has been classified as problematic. This affects some unknown functionality of the component Performance Counter. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability.

The weakness was shared 06/21/1999. Neither technical details nor an exploit are publicly available.

Upgrading to version 2000 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (3568), SecurityFocus (BID 486†) and Vulnerability Center (SBV-2368†). The entry VDB-88630 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Operating System

Vendor

Microsoft

Name

Windows

Version

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: 3.3
VulDB Meta Temp Score: 3.2

VulDB Base Score: 3.3
VulDB Temp Score: 3.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: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Windows 2000

Timelineinfo

06/21/1999 🔍
06/21/1999 +0 days 🔍
06/21/1999 +0 days 🔍
10/14/2003 +1576 days 🔍
07/05/2016 +4648 days 🔍
02/16/2019 +956 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Status: Not defined

GCVE (VulDB): GCVE-100-88629
X-Force: 3568
SecurityFocus: 486 - NT Performance Counters Memory Leak Vulnerability
Vulnerability Center: 2368 - Windows NT Non-Available Performance Counters Results in Memory Leakage, Medium

See also: 🔍

Entryinfo

Created: 07/05/2016 12:11
Updated: 02/16/2019 15:25
Changes: 07/05/2016 12:11 (37), 02/16/2019 15:25 (12)
Complete: 🔍
Cache ID: 216::103

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