Microsoft Windows NT 3.1/NT 3.5/NT 3.51/NT 4.0 privileges management

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

Summaryinfo

A vulnerability, which was classified as critical, has been found in Microsoft Windows NT 3.1/NT 3.5/NT 3.51/NT 4.0. Affected is an unknown function. Performing a manipulation results in privileges management. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Microsoft Windows NT 3.1/NT 3.5/NT 3.51/NT 4.0 (Operating System). This affects an unknown functionality. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was disclosed 06/01/1998. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 2000 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-4285†). The entry VDB-89520 is pretty similar. 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: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Privileges management
CWE: CWE-269 / CWE-266
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/01/1998 🔍
06/01/1998 +0 days 🔍
05/10/2004 +2170 days 🔍
07/16/2016 +4450 days 🔍
02/28/2019 +957 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Status: Not defined

GCVE (VulDB): GCVE-100-89517
Vulnerability Center: 4285 - [MS98-001] Microsoft Windows NT Local Domain Group Creation by Under Privileges Users, Low

See also: 🔍

Entryinfo

Created: 07/16/2016 23:13
Updated: 02/28/2019 09:51
Changes: 07/16/2016 23:13 (36), 02/28/2019 09:51 (8)
Complete: 🔍
Cache ID: 216::103

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