| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows 10/Server 2016. It has been declared as problematic. Affected is an unknown function of the component Device Guard. Executing a manipulation can lead to access control. This vulnerability is tracked as CVE-2017-11823. The attack is restricted to local execution. Moreover, an exploit is present. A patch should be applied to remediate this issue.
Details
A vulnerability classified as problematic was found in Microsoft Windows 10/Server 2016 (Operating System). This vulnerability affects some unknown processing of the component Device Guard. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The Microsoft Device Guard on Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows a security feature bypass by the way it handles Windows PowerShell sessions, aka "Microsoft Windows Security Feature Bypass".
The bug was discovered 10/10/2017. The weakness was disclosed 10/10/2017 by James Forshaw with Google Project Zero as KB4042895 as confirmed security update guide (Website). The advisory is available at portal.msrc.microsoft.com. This vulnerability was named CVE-2017-11823 since 07/31/2017. The exploitation appears to be difficult. Local access is required to approach this attack. Required for exploitation is a single authentication. Successful exploitation requires user interaction by the victim. Technical details are unknown but a public exploit is available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project. The advisory points out:
A security feature bypass vulnerability exists in Device Guard that could allow an attacker to inject malicious code into a Windows PowerShell session. An attacker who successfully exploited this vulnerability could inject code into a trusted PowerShell process to bypass the Device Guard Code Integrity policy on the local machine.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 103745 (KB4041676: Windows 10 Version 1703 October 2017 Cumulative Update (KRACK)), 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 91411 (Microsoft Windows Security Update October 2017 (KRACK Attack) (ROCA)).
Applying the patch KB4042895 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 (42997), Tenable (103745) and SecurityFocus (BID 101102†). The entries VDB-107699, VDB-107701, VDB-107702 and VDB-107704 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit 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: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 6.3
Vendor Vector (Microsoft): 🔍
NVD Base Score: 6.7
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
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 103745
Nessus Name: KB4041676: Windows 10 Version 1703 October 2017 Cumulative Update (KRACK)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 802136
OpenVAS Name: Microsoft Windows Multiple Vulnerabilities (KB4042895)
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: 🔍
Patch: KB4042895
Timeline
07/31/2017 🔍10/10/2017 🔍
10/10/2017 🔍
10/10/2017 🔍
10/10/2017 🔍
10/10/2017 🔍
10/11/2017 🔍
10/13/2017 🔍
09/10/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: KB4042895
Researcher: James Forshaw
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-11823 (🔍)
GCVE (CVE): GCVE-0-2017-11823
GCVE (VulDB): GCVE-100-107722
OVAL: 🔍
SecurityFocus: 101102 - Microsoft Windows Device Guard CVE-2017-11823 Local Security Bypass Vulnerability
SecurityTracker: 1039526
scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔍
Entry
Created: 10/11/2017 23:38Updated: 09/10/2024 21:09
Changes: 10/11/2017 23:38 (88), 11/23/2019 17:12 (10), 01/16/2021 12:16 (2), 09/10/2024 21:09 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.