Microsoft Windows NT 4.0 Kernel Mode Address GetThreadContext/SetThreadContext denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows NT 4.0. It has been classified as problematic. Affected by this issue is the function GetThreadContext/SetThreadContext of the component Kernel Mode Address Handler. This manipulation causes denial of service.
This vulnerability is handled as CVE-1999-1364. It is possible to launch the attack on the local host. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Microsoft Windows NT 4.0 (Operating System). It has been declared as problematic. Affected by this vulnerability is the function GetThreadContext/SetThreadContext of the component Kernel Mode Address Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
Windows NT 4.0 allows local users to cause a denial of service (crash) via an illegal kernel mode address to the functions (1) GetThreadContext or (2) SetThreadContext.
The weakness was released 12/31/1999 as confirmed knowledge base article (Website). The advisory is shared at support.microsoft.com. This vulnerability is known as CVE-1999-1364. The exploitation appears to be easy. An attack has to be approached locally. The requirement for exploitation is a single authentication. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (7421). Entries connected to this vulnerability are available at VDB-15180, VDB-15179, VDB-15178 and VDB-15177. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
12/31/1999 🔍12/31/1999 🔍
06/23/2014 🔍
06/08/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: support.microsoft.com
Status: Confirmed
CVE: CVE-1999-1364 (🔍)
GCVE (CVE): GCVE-0-1999-1364
GCVE (VulDB): GCVE-100-15181
X-Force: 7421
See also: 🔍
Entry
Created: 06/23/2014 12:59Updated: 06/08/2024 11:59
Changes: 06/23/2014 12:59 (40), 04/07/2017 16:02 (10), 06/08/2024 11:59 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.