Microsoft Windows up to Server 2016 Device Guard Code Integrity Policy 7pk security

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.5$5k-$25k0.00

Summaryinfo

A vulnerability classified as critical has been found in Microsoft Windows up to Server 2016. Affected by this issue is some unknown functionality of the component Device Guard Code Integrity Policy. This manipulation causes 7pk security. This vulnerability is handled as CVE-2018-8212. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in Microsoft Windows up to Server 2016 (Operating System) and classified as critical. Affected by this vulnerability is some unknown processing of the component Device Guard Code Integrity Policy. The manipulation with an unknown input leads to a 7pk security vulnerability. The CWE definition for the vulnerability is CWE-254. As an impact it is known to affect confidentiality, integrity, and availability.

The bug was discovered 06/12/2018. The weakness was released 06/12/2018 by Matt as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The public release was coordinated with Microsoft. This vulnerability is known as CVE-2018-8212 since 03/14/2018. The attack can be launched remotely. Required for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/27/2023). MITRE ATT&CK project uses the attack technique T1211 for this issue. 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.

The vulnerability scanner Nessus provides a plugin with the ID 110487 (KB4284835: Windows 10 Version 1803 and Windows Server Version 1803 June 2018 Security 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 91452 (Microsoft Windows Security Update June 2018).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (110487) and SecurityFocus (BID 104328†). Entries connected to this vulnerability are available at VDB-119431, VDB-119432, VDB-119433 and VDB-119434. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 5.3
Vendor Vector (Microsoft): 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: 7pk security
CWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 110487
Nessus Name: KB4284835: Windows 10 Version 1803 and Windows Server Version 1803 June 2018 Security Update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

03/14/2018 🔍
06/12/2018 +90 days 🔍
06/12/2018 +0 days 🔍
06/12/2018 +0 days 🔍
06/12/2018 +0 days 🔍
06/12/2018 +0 days 🔍
06/13/2018 +1 days 🔍
06/14/2018 +0 days 🔍
03/27/2023 +1747 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: portal.msrc.microsoft.com
Researcher: Matt
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2018-8212 (🔍)
GCVE (CVE): GCVE-0-2018-8212
GCVE (VulDB): GCVE-100-119461

OVAL: 🔍

SecurityFocus: 104328 - Microsoft Windows Device Guard CVE-2018-8212 Local Security Bypass Vulnerability
SecurityTracker: 1041098

scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔍

Entryinfo

Created: 06/13/2018 18:42
Updated: 03/27/2023 08:14
Changes: 06/13/2018 18:42 (86), 02/18/2020 20:31 (6), 03/27/2023 08:14 (5)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!