CVE-2018-8256: Critical severity microsoft.powershell.archive vulnerability

Published Nov 14, 2018

Updated

A remote code execution vulnerability exists when PowerShell improperly handles specially crafted files, aka "Microsoft PowerShell Remote Code Execution Vulnerability." This affects Windows RT 8.1, PowerShell Core 6.0, Microsoft.PowerShell.Archive 1.2.2.0, Windows Server 2016, Windows Server 2012, Windows Server 2008 R2, Windows Server 2019, Windows 7, Windows Server 2012 R2, PowerShell Core 6.1, Windows 10 Servers, Windows 10, Windows 8.1.

Affected Software

20 affected components

Microsoft Microsoft.PowerShell.Archive=1.2.2.0

Microsoft PowerShell Core=6.0

Microsoft PowerShell Core=6.1

Microsoft Windows 10

Microsoft Windows 10=1607

Microsoft Windows 10=1703

Microsoft Windows 10=1709

Microsoft Windows 10=1803

Microsoft Windows 10=1809

Microsoft Windows 7=sp1

Microsoft Windows 8.1

Microsoft Windows RT 8.1

Microsoft Windows Server 2008=r2-sp1

Microsoft Windows Server 2012

Microsoft Windows Server 2012=r2

Microsoft Windows Server 2016

Microsoft Windows Server 2016=1709

Microsoft Windows Server 2016=1803

Microsoft Windows Server 2019

Remediation

Patch Available

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8256

Event History

Nov 14, 2018

CVE Published

via MITRE·01:00 AM

Data Sourced

via MITRE·01:00 AM

DescriptionWeakness

Frequently Asked Questions

What is CVE-2018-8256?

CVE-2018-8256 is a remote code execution vulnerability in Microsoft PowerShell.

How does CVE-2018-8256 affect Windows?

CVE-2018-8256 affects Windows RT 8.1, PowerShell Core 6.0, and various versions of Windows 10, Windows 7, Windows 8.1, and Windows Server.

What is the severity of CVE-2018-8256?

CVE-2018-8256 is classified as critical with a severity value of 8.8.

How can I fix CVE-2018-8256?

Apply the necessary security updates provided by Microsoft for the affected software versions.

Where can I find more information about CVE-2018-8256?

You can find more information about CVE-2018-8256 on the Microsoft Security website.