Microsoft Windows up to Server 2016 Kernel nt!NtQueryInformationResourceManager Kernel Memory information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows up to Server 2016 and classified as problematic. The impacted element is the function nt!NtQueryInformationResourceManager of the component Kernel. Such manipulation leads to information disclosure (Kernel Memory).
This vulnerability is listed as CVE-2017-8481. The attack must be carried out locally. In addition, an exploit is available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Microsoft Windows up to Server 2016 (Operating System). It has been rated as problematic. Affected by this issue is the function nt!NtQueryInformationResourceManager of the component Kernel. The manipulation with an unknown input leads to a information disclosure vulnerability (Kernel Memory). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The bug was discovered 06/13/2017. The weakness was presented 06/13/2017 by Mateusz Jurczyk with Google Project Zero as KB4022013 as confirmed security update guide (Website). The advisory is shared for download at portal.msrc.microsoft.com. This vulnerability is handled as CVE-2017-8481 since 05/03/2017. The attack needs to be approached locally. A simple authentication is needed for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1592. The advisory points out:
An information disclosure vulnerability exists when the Windows kernel improperly initializes objects in memory. To exploit this vulnerability, an authenticated attacker could run a specially crafted application. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user’s system. The update addresses the vulnerability by correcting how the Windows kernel initializes objects in memory.
A public exploit has been developed by Google Security Research in C++ and been published 2 weeks after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 100759 (KB4022714: Windows 10 Version 1511 June 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 91385 (Microsoft Windows Security Update June 2017).
Applying the patch KB4022013 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 Exploit-DB (42242), Tenable (100759) and SecurityFocus (BID 98862†). See VDB-102373, VDB-102374, VDB-102375 and VDB-102376 for similar entries. Once again VulDB remains the best source for vulnerability data.
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: 5.1VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 4.7
Vendor Vector (Microsoft): 🔍
NVD Base Score: 5.0
NVD Vector: 🔍
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
Name: Kernel MemoryClass: Information disclosure / Kernel Memory
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Google Security Research
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 100759
Nessus Name: KB4022714: Windows 10 Version 1511 June 2017 Cumulative Update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 802136
OpenVAS Name: Microsoft Windows Multiple Vulnerabilites (KB4022719)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Patch: KB4022013
Timeline
05/03/2017 🔍06/13/2017 🔍
06/13/2017 🔍
06/13/2017 🔍
06/13/2017 🔍
06/13/2017 🔍
06/14/2017 🔍
06/14/2017 🔍
06/23/2017 🔍
06/23/2017 🔍
08/21/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: KB4022013
Researcher: Mateusz Jurczyk
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-8481 (🔍)
GCVE (CVE): GCVE-0-2017-8481
GCVE (VulDB): GCVE-100-102428
OVAL: 🔍
SecurityFocus: 98862 - Microsoft Windows Kernel CVE-2017-8481 Local Information Disclosure Vulnerability
SecurityTracker: 1038659
scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔍
Entry
Created: 06/14/2017 11:24Updated: 08/21/2024 15:26
Changes: 06/14/2017 11:24 (98), 10/20/2019 10:32 (7), 12/28/2020 09:37 (3), 08/21/2024 15:26 (17)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.