{
	"id": "46437f55-408e-4b38-a6d4-f8416bbf2909",
	"created_at": "2026-04-06T00:13:52.370219Z",
	"updated_at": "2026-04-10T13:11:48.120076Z",
	"deleted_at": null,
	"sha1_hash": "becd011c00d25d50f50a3b6cb99360647475e0e5",
	"title": "MS14-025: Vulnerability in Group Policy Preferences could allow elevation of privilege: May 13, 2014",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 558792,
	"plain_text": "MS14-025: Vulnerability in Group Policy Preferences could allow\r\nelevation of privilege: May 13, 2014\r\nArchived: 2026-04-05 19:48:39 UTC\r\nINTRODUCTION\r\nMicrosoft has released security bulletin MS14-025. To learn more about this security bulletin:\r\nHome users:\r\nhttps://www.microsoft.com/security/pc-security/updates.aspxSkip the details: Download the updates for your home\r\ncomputer or laptop from the Microsoft Update website now:\r\nhttps://update.microsoft.com/microsoftupdate/\r\nIT professionals:\r\nhttps://technet.microsoft.com/security/bulletin/MS14-025\r\nHow to obtain help and support for this security update\r\nMore Information\r\nKnown issues and more information about this security update\r\nThe following articles contain more information about this security update as it relates to individual product versions. The\r\narticles may contain known issue information. If this is the case, the known issue is listed under each article link.\r\n2928120\r\nMS14-025: Description of the security update for Windows Remote Server Administration Tools for systems that\r\nhave update 2919355 installed: May 13, 2014\r\n2961899\r\nMS14-025: Description of the security update for Windows Remote Server Administration Tools for systems that do\r\nnot have update 2919355 installed: May 13, 2014\r\nGroup Policy Preferences\r\nOverview\r\nSome Group Policy Preferences can store a password. This functionality is being removed because the password was stored\r\ninsecurely. This article describes the user interface changes and any available workarounds.\r\nThe following Group Policy Preferences will no longer allow user names and passwords to be saved:\r\nDrive Maps\r\nLocal Users and Groups\r\nScheduled Tasks\r\nServices\r\nData Sources\r\nThis will affect the behavior of any existing Group Policy Objects (GPOs) in your environment that rely on passwords that\r\nare contained in these preferences. It will also prevent creating new Group Policy Preferences by using this functionality.\r\nFor Drive Maps, Local Users and Groups, and Services, you may be able to achieve similar goals through other, more secure\r\nfunctionality in Windows.\r\nFor Scheduled Tasks and Data Sources, you will be unable to achieve the same goals that were available through the\r\nnonsecure functionality of Group Policy Preferences passwords.\r\nScenarios\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 1 of 14\n\nThe following Group Policy Preferences are affected by this change. Each preference is covered briefly and then in more\r\ndetail. Additionally, workarounds are provided that enable you to perform the same tasks.\r\nAffected preference Applies to user Applies to computer\r\nLocal user management Yes Yes\r\nMapped drives Yes No\r\nServices No Yes\r\nScheduled tasks (up-level) Yes Yes\r\nScheduled tasks (down-level) Yes Yes\r\nImmediate tasks (up-level) Yes Yes\r\nImmediate tasks (down-level) Yes Yes\r\nData sources Yes Yes\r\nSummary of changes\r\nPassword fields in all affected preferences are disabled. Administrators cannot create new preferences by using these\r\npassword fields.\r\nThe username field is disabled in some preferences.\r\nExisting preferences that contain a password cannot be updated. They can only be deleted or disabled, as appropriate\r\nfor the specific preference.\r\nThe behavior for Delete and Disable actions have not changed for the preferences.\r\nWhen an administrator opens any preference that contains the CPassword attribute, the administrator receives the\r\nfollowing warning dialog box to inform him or her of the recent deprecation. Attempts to save changes to new or\r\nexisting preferences that require the CPassword attribute will trigger the same dialog box. Only Delete and Disable\r\nactions will not trigger warning dialog boxes.\r\nScenario 1: Local user management\r\nThe Local User Management preference is frequently used to create local administrators who have a known password on a\r\ncomputer. This feature is not secure because of the way that Group Policy Preferences stores passwords. Therefore, this\r\nfunctionality is no longer available. The following preferences are affected:\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Local Users and Groups-\u003e New-\u003e Local User\r\nUser Configuration -\u003e Control Panel Settings -\u003e Local Users and Groups-\u003e New-\u003e Local User\r\nImportant changes\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 2 of 14\n\nAction: Create or Replace\r\nThe User name, Password, and Confirm Password fields are disabled.\r\nThe warning dialog box appears when the administrator opens or tries to save any changes to an existing preference\r\nthat contains a password.\r\nAction: Update\r\nThe Password and Confirm Password fields are disabled.\r\nThe warning dialog box appears when the administrator opens or tries to save any changes to an existing preference\r\nthat contains a password.\r\nAction: Delete\r\nNo change in behavior\r\nWorkarounds\r\nFor those who previously relied on the Group Policy Preference for setting local administrator passwords, the following\r\nscript is provided as a secure alternative to CPassword. Copy and save the contents to a new Windows PowerShell file, and\r\nthen run the script as indicated in its .EXAMPLE section.\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 3 of 14\n\nMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes,\r\nbut is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that\r\nyou are familiar with the programming language that is being demonstrated and with the tools that are used to create and to\r\ndebug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they\r\nwill not modify these examples to provide added functionality or construct procedures to meet your specific requirements.\r\nfunction Invoke-PasswordRoll{\u003c#.SYNOPSIS\r\nThis script can be used to set the local account passwords on remote machines to random passwords. The\r\nusername/password/server combination will be saved in a CSV file.The account passwords stored in the CSV file can be\r\nencrypted using a password of the administrators choosing to ensure clear-text account passwords aren't written to disk.The\r\nencrypted passwords can be decrypted using another function in this file: ConvertTo-CleartextPassword\r\nFunction: Invoke-PasswordRollAuthor: MicrosoftVersion: 1.0\r\n.DESCRIPTION\r\nThis script can be used to set the local account passwords on remote machines to random passwords. The\r\nusername/password/server combination will be saved in a CSV file.The account passwords stored in the CSV file can be\r\nencrypted using a password of the administrators choosing to ensure clear-text account passwords aren't written to disk.The\r\nencrypted passwords can be decrypted using another function in this file: ConvertTo-CleartextPassword\r\n.PARAMETER ComputerName\r\nAn array of computers to run the script against using PowerShell remoting.\r\n.PARAMETER LocalAccounts\r\nAn array of local accounts whose password should be changed.\r\n.PARAMETER TsvFileName\r\nThe file to output the username/password/server combinations to.\r\n.PARAMETER EncryptionKey\r\nA password to encrypt the TSV file with. Uses AES encryption. Only the passwords stored in the TSV file will be encrypted,\r\nthe username and servername will be clear-text.\r\n.PARAMETER PasswordLength\r\nThe length of the passwords which will be randomly generated for local accounts.\r\n.PARAMETER NoEncryption\r\nDo not encrypt the account passwords stored in the TSV file. This will result in clear-text passwords being written to disk.\r\n.EXAMPLE\r\n. .\\Invoke-PasswordRoll.ps1 #Loads the functions in this script fileInvoke-PasswordRoll -ComputerName (Get-Content\r\ncomputerlist.txt) -LocalAccounts @(\"administrator\",\"CustomLocalAdmin\") -TsvFileName \"LocalAdminCredentials.tsv\" -\r\nEncryptionKey \"Password1\"\r\nConnects to all the computers stored in the file \"computerlist.txt\". If the local account \"administrator\" and/or\r\n\"CustomLocalAdmin\" are present on the system, their password is changedto a randomly generated password of length 20\r\n(the default). The username/password/server combinations are stored in LocalAdminCredentials.tsv, and the account\r\npasswords are AES encrypted using the password \"Password1\".\r\n.EXAMPLE\r\n. .\\Invoke-PasswordRoll.ps1 #Loads the functions in this script fileInvoke-PasswordRoll -ComputerName (Get-Content\r\ncomputerlist.txt) -LocalAccounts @(\"administrator\") -TsvFileName \"LocalAdminCredentials.tsv\" -NoEncryption -\r\nPasswordLength 40\r\nConnects to all the computers stored in the file \"computerlist.txt\". If the local account \"administrator\" is present on the\r\nsystem, its password is changed to a random generatedpassword of length 40. The username/password/server combinations\r\nare stored in LocalAdminCredentials.tsv unencrypted.\r\n.NOTESRequirements: -PowerShellv2 or above must be installed-PowerShell remoting must be enabled on all systems the\r\nscript will be run against\r\nScript behavior:-If a local account is present on the system, but not specified in the LocalAccounts parameter, the script will\r\nwrite a warning to the screen to alert you to the presence of this local account. The script will continue running when this\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 4 of 14\n\nhappens.-If a local account is specified in the LocalAccounts parameter, but the account does not exist on the computer,\r\nnothing will happen (an account will NOT be created).-The function ConvertTo-CleartextPassword, contained in this file,\r\ncan be used to decrypt passwords that are stored encrypted in the TSV file.-If a server specified in ComputerName cannot be\r\nconnected to, PowerShell will output an error message.-Microsoft advises companies to regularly roll all local and domain\r\naccount passwords.\r\n#\u003e [CmdletBinding(DefaultParameterSetName=\"Encryption\")] Param( [Parameter(Mandatory=$true)] [String[]]\r\n$ComputerName,\r\n[Parameter(Mandatory=$true)] [String[]] $LocalAccounts,\r\n[Parameter(Mandatory=$true)] [String] $TsvFileName,\r\n[Parameter(ParameterSetName=\"Encryption\", Mandatory=$true)] [String] $EncryptionKey,\r\n[Parameter()] [ValidateRange(20,120)] [Int] $PasswordLength = 20,\r\n[Parameter(ParameterSetName=\"NoEncryption\", Mandatory=$true)] [Switch] $NoEncryption )\r\n#Load any needed .net classes Add-Type -AssemblyName \"System.Web\" -ErrorAction Stop\r\n#This is the scriptblock that will be executed on every computer specified in ComputerName $RemoteRollScript = { Param(\r\n[Parameter(Mandatory=$true, Position=1)] [String[]] $Passwords,\r\n[Parameter(Mandatory=$true, Position=2)] [String[]] $LocalAccounts,\r\n#This is here so I can record what the server name that the script connected to was, sometimes the DNS records get messed\r\nup, it can be nice to have this. [Parameter(Mandatory=$true, Position=3)] [String] $TargettedServerName )\r\n$LocalUsers = Get-WmiObject Win32_UserAccount -Filter \"LocalAccount=true\" | Foreach {$_.Name}\r\n#Check if the computer has any local user accounts whose passwords are not going to be rolled by this script foreach ($User\r\nin $LocalUsers) { if ($LocalAccounts -inotcontains $User) { Write-Warning \"Server: '$($TargettedServerName)' has a local\r\naccount '$($User)' whos password is NOT being changed by this script\" } }\r\n#For every local account specified that exists on this server, change the password $PasswordIndex = 0 foreach\r\n($LocalAdmin in $LocalAccounts) { $Password = $Passwords[$PasswordIndex]\r\nif ($LocalUsers -icontains $LocalAdmin) { try { $objUser = [ADSI]\"WinNT://localhost/$($LocalAdmin), user\"\r\n$objUser.psbase.Invoke(\"SetPassword\", $Password)\r\n$Properties = @{ TargettedServerName = $TargettedServerName Username = $LocalAdmin Password = $Password\r\nRealServerName = $env:computername }\r\n$ReturnData = New-Object PSObject -Property $Properties Write-Output $ReturnData } catch { Write-Error \"Error\r\nchanging password for user:$($LocalAdmin) on server:$($TargettedServerName)\" } }\r\n$PasswordIndex++ } }\r\n#Generate the password on the client running this script, not on the remote machine. System.Web.Security isn't available in\r\nthe .NET Client profile. Making this call # on the client running the script ensures only 1 computer needs the full .NET\r\nruntime installed (as opposed to every system having the password rolled). function Create-RandomPassword { Param(\r\n[Parameter(Mandatory=$true)] [ValidateRange(20,120)] [Int] $PasswordLength )\r\n$Password = [System.Web.Security.Membership]::GeneratePassword($PasswordLength, $PasswordLength / 4)\r\n#This should never fail, but I'm putting a sanity check here anyways if ($Password.Length -ne $PasswordLength) { throw\r\nnew Exception(\"Password returned by GeneratePassword is not the same length as required. Required length:\r\n$($PasswordLength). Generated length: $($Password.Length)\") }\r\nreturn $Password }\r\n#Main functionality - Generate a password and remote in to machines to change the password of local accounts specified if\r\n($PsCmdlet.ParameterSetName -ieq \"Encryption\") { try { $Sha256 = new-object\r\nSystem.Security.Cryptography.SHA256CryptoServiceProvider $SecureStringKey =\r\n$Sha256.ComputeHash([System.Text.UnicodeEncoding]::Unicode.GetBytes($EncryptionKey)) } catch { Write-Error \"Error\r\ncreating TSV encryption key\" -ErrorAction Stop } }\r\nforeach ($Computer in $ComputerName) { #Need to generate 1 password for each account that could be changed\r\n$Passwords = @() for ($i = 0; $i -lt $LocalAccounts.Length; $i++) { $Passwords += Create-RandomPassword -\r\nPasswordLength $PasswordLength }\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 5 of 14\n\nWrite-Output \"Connecting to server '$($Computer)' to roll specified local admin passwords\" $Result = Invoke-Command -\r\nScriptBlock $RemoteRollScript -ArgumentList @($Passwords, $LocalAccounts, $Computer) -ComputerName $Computer\r\n#If encryption is being used, encrypt the password with the user supplied key prior to writing to disk if ($Result -ne $null) {\r\nif ($PsCmdlet.ParameterSetName -ieq \"NoEncryption\") { $Result | Select-Object\r\nUsername,Password,TargettedServerName,RealServerName | Export-Csv -Append -Path $TsvFileName -\r\nNoTypeInformation } else { #Filters out $null entries returned $Result = $Result | Select-Object\r\nUsername,Password,TargettedServerName,RealServerName\r\nforeach ($Record in $Result) { $PasswordSecureString = ConvertTo-SecureString -AsPlainText -Force -String\r\n($Record.Password) $Record | Add-Member -MemberType NoteProperty -Name EncryptedPassword -Value (ConvertFrom-SecureString -Key $SecureStringKey -SecureString $PasswordSecureString)\r\n$Record.PSObject.Properties.Remove(\"Password\") $Record | Select-Object\r\nUsername,EncryptedPassword,TargettedServerName,RealServerName | Export-Csv -Append -Path $TsvFileName -\r\nNoTypeInformation } } } }}\r\nfunction ConvertTo-CleartextPassword{\u003c#.SYNOPSISThis function can be used to decrypt passwords that were stored\r\nencrypted by the function Invoke-PasswordRoll.\r\nFunction: ConvertTo-CleartextPasswordAuthor: MicrosoftVersion: 1.0\r\n.DESCRIPTIONThis function can be used to decrypt passwords that were stored encrypted by the function Invoke-PasswordRoll.\r\n.PARAMETER EncryptedPassword\r\nThe encrypted password that was stored in a TSV file.\r\n.PARAMETER EncryptionKey\r\nThe password used to do the encryption.\r\n.EXAMPLE\r\n. .\\Invoke-PasswordRoll.ps1 #Loads the functions in this script fileConvertTo-CleartextPassword -EncryptionKey\r\n\"Password1\" -EncryptedPassword\r\n76492d1116743f0423413b16050a5345MgB8AGcAZgBaAHUAaQBwADAAQgB2AGgAcABNADMASwBaAFoAQQBzADEAeABjAEEAPQA9AHw\r\nDecrypts the encrypted password which was stored in the TSV file.\r\n#\u003e Param( [Parameter(Mandatory=$true)] [String] $EncryptedPassword,\r\n[Parameter(Mandatory=$true)] [String] $EncryptionKey )\r\n$Sha256 = new-object System.Security.Cryptography.SHA256CryptoServiceProvider $SecureStringKey =\r\n$Sha256.ComputeHash([System.Text.UnicodeEncoding]::Unicode.GetBytes($EncryptionKey))\r\n[SecureString]$SecureStringPassword = ConvertTo-SecureString -String $EncryptedPassword -Key $SecureStringKey\r\nWrite-Output\r\n([System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToCoTaskMemUnicode($SecureS\r\n  Administrators can add local administrator accounts to computers by creating an Active Directory group and adding it to\r\nthe local Administrators group through Group Policy Preferences -\u003e Local Group. This action does not cache credentials.\r\nThe dialog box resembles the following. This workaround does require a connection to Active Directory Domain Services\r\nwhen the user is logged on by using these credentials.\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 6 of 14\n\nScenario 2: Mapped drives\r\nAdministrators use drive maps to allocate network locations to users. The password protection feature is used to make sure\r\nof authorized access to the drive. The following preferences are affected:\r\nUser Configuration -\u003e Windows Settings -\u003e Drive Maps -\u003e New -\u003e Mapped Drive\r\nImportant changes\r\nAction: Create, Update, or Replace\r\nThe User name, Password, and Confirm password fields are disabled.\r\nAction: Delete\r\nNo change in behavior\r\nWorkarounds\r\nInstead of using the password method for authentication, you can use Windows Explorer to manage share permissions and\r\nallocate rights to users. You can use Active Directory objects to control permissions to the folder.\r\nScenario 3: Services\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 7 of 14\n\nYou can use the Services preference to change service properties in such a way that they run in a context other than their\r\noriginal security context. The following preferences are affected:\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Services -\u003e New -\u003e Service\r\nImportant changes\r\nStartup: No Change, Automatic, or Manual\r\nThe Password and Confirm password fields are disabled.\r\nThe administrator can use only built-in accounts.\r\nStartup: Disable\r\nNo change in behavior\r\nNew dialog box\r\nAdministrators who try to use non-built-in users for This account\" receive the following warning:\r\nWorkarounds\r\nServices can still run as a local system account. Service permissions can be altered as documented in the following article in\r\nthe Microsoft Knowledge Base:\r\n256345 How to Configure Group Policy settings to set security for system services\r\nNote If the service that you want to configure is not present, you must configure the settings on a computer that has the\r\nservice running. \r\nScenario 4: Scheduled and immediate tasks (up-level)\r\nThese are used to run scheduled tasks in a specific security context. The ability to store credentials for scheduled tasks to run\r\nas an arbitrary user when that user is not logged on is no longer available. The following preferences are affected. (Be aware\r\nthat on some platforms, \"At least Windows 7\" is replaced with \"Windows Vista and later.\")\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 8 of 14\n\nComputer Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Scheduled Task (At least Windows\r\n7)\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Immediate Task (At least Windows\r\n7)\r\nUser Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Scheduled Task (At least Windows 7)\r\nUser Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Immediate Task (At least Windows 7)\r\nImportant changes\r\nAction: Create, Update, or Replace\r\nWhen you select the Run whether user is logged on or not option, a dialog box no longer prompts the administrator\r\nfor credentials.\r\nThe Do not store password check box is disabled. By default, the box is also checked.\r\nAction: Delete\r\nNo change in behavior\r\nWorkarounds\r\nFor the \"Scheduled Task (at least Windows 7)\" and \"Immediate Task (at least Windows 7)\" tasks, administrators can use\r\nspecific user accounts when the given user is logged on. Or, they can only have access to local resources as that user. These\r\ntasks still can run in the context of the local service.\r\nScenario 5: Scheduled and immediate tasks (down-level) This is the down-level version of preferences used to run\r\nScheduled Tasks in a specific security context. The ability to store credentials for scheduled tasks to run as an arbitrary user\r\nwhen that user is not logged on is no longer available. The following preferences are affected:\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Scheduled Task\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Immediate Task (Windows XP)\r\nUser Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Scheduled Task\r\nUser Configuration -\u003e Control Panel Settings -\u003e Scheduled Tasks -\u003e New -\u003e Immediate Task (Windows XP)\r\nImportant changes\r\nAction: Create, Update, or Replace\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 9 of 14\n\nThe Run as check box is disabled. Therefore, the User Name, Password, and Confirm Password fields are all\r\ndisabled.\r\nAction: Delete\r\nNo change in behavior\r\nWorkarounds\r\nFor the \"Scheduled Task\" and \"Immediate Task (Windows XP)\" items, scheduled tasks run by using the permissions that are\r\ncurrently available to the local service. \r\nScenario 6: Data Sources\r\nThe Data Sources preference is used to associate a data source with a computer or user. This feature no longer stores\r\ncredentials to enable access to data sources that are protected by a password. The following preferences are affected:\r\nComputer Configuration -\u003e Control Panel Settings -\u003e Data Sources\r\nUser Configuration -\u003e Control Panel Settings -\u003e Data Sources\r\nImportant Changes\r\nAction: Create, Update, or Replace\r\nThe User Name, Password, and Confirm Password fields are disabled:\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 10 of 14\n\nAction: Delete\r\nNo change in behavior\r\nWorkarounds\r\nNo workarounds are available. This preference no longer stores credentials to allow access to data sources that are protected\r\nby a password. \r\nDeprecation of CPassword\r\nRemoving CPassword\r\nThe Windows PowerShell script that is included in this Microsoft Knowledge Base article detects whether a domain\r\ncontains any Group Policy Preferences that might use CPassword. If CPassword XML is detected in a given preference, it is\r\ndisplayed in this list. \r\nDetecting CPassword preferences\r\nThis script must be run from a local directory on the domain controller that you want to clean. Copy and save the contents to\r\na new Windows PowerShell file, determine your system drive, and then run the script as indicated in the following usage.\r\n\u003c#.SYNOPSISGroup Policy objects in your domain can have preferences that store passwords for different tasks, such as\r\nthe following: 1. Data Sources 2. Drive Maps 3. Local Users 4. Scheduled Tasks (both XP and up-level) 5. ServicesThese\r\npasswords are stored in SYSVOL as part of GP preferences and are not secure because of weak encryption (32-byte AES).\r\nTherefore, we recommend that you not deploy such preferences in your domain environment and remove any such existing\r\npreferences. This script is to help administrator find GP Preferences in their domain's SYSVOL that contains passwords.\r\n.DESCRIPTIONThis script should be run on a DC or a client computer that is installed with RSAT to print all the\r\npreferences that contain password with information such as GPO, Preference Name, GPEdit path under which this\r\npreference is defined.After you have a list of affected preferences, these preferences can be removed by using the editor in\r\nthe Group Policy Management Console.\r\n.SYNTAXGet-SettingsWithCPassword.ps1 [-Path \u003cString\u003e] .EXAMPLEGet-SettingsWithCPassword.ps1 -Path\r\n%WinDir%\\SYSVOL\\domainGet-SettingsWithCPassword.ps1 -Path \u003cGPO Backup Folder Path\u003e\r\n.NOTESIf Group Policy PS module is not found the output will contain GPO GUIDs instead of GPO names. You can either\r\nrun this script on a domain controller or rerun the script on the client after you have installed RSAT and enabled the Group\r\nPolicy module.Or, you can use GPO GUIDs to obtain GPO names by using the Get-GPO cmdlet.\r\n.LINKhttp://go.microsoft.com/fwlink/?LinkID=390507\r\n#\u003e#----------------------------------------------------------------------------------------------------------------# Input parameters#---------\r\n-----------------------------------------------------------------------------------------------------param( [string]$Path = $(throw \"-Path is\r\nrequired.\") # Directory path where GPPs are located. )#-----------------------------------------------------------------------------------\r\n----------------------------$isGPModuleAvailable = $false$impactedPrefs = { \"Groups.xml\",\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 11 of 14\n\n\"ScheduledTasks.xml\",\"Services.xml\", \"DataSources.xml\", \"Drives.xml\" }#----------------------------------------------------------\r\n------------------------------------------------------# import Group olicy module if available#---------------------------------------------\r\n-------------------------------------------------------------------if (-not (Get-Module -name \"GroupPolicy\")){ if (Get-Module -\r\nListAvailable | Where-Object { $_.Name -ieq \"GroupPolicy\" }) { $isGPModuleAvailable = $true Import-Module\r\n\"GroupPolicy\" } else { Write-Warning \"Unable to import Group Policy module for PowerShell. Therefore, GPO guids will\r\nbe reported. Run this script on DC to obtain the GPO names, or use the Get-GPO cmdlet (on DC) to obtain the GPO name\r\nfrom GPO guid.\" }}else{ $isGPModuleAvailable = $true}Function Enum-SettingsWithCpassword ( [string]$sysvolLocation\r\n){ # GPMC tree paths $commonPath = \" -\u003e Preferences -\u003e Control Panel Settings -\u003e \" $driveMapPath = \" -\u003e Preferences -\u003e\r\nWindows Settings -\u003e \"\r\n# Recursively obtain all the xml files within the SYVOL location $impactedXmls = Get-ChildItem $sysvolLocation -\r\nRecurse -Filter \"*.xml\" | Where-Object { $impactedPrefs -cmatch $_.Name }\r\n# Each xml file contains multiple preferences. Iterate through each preference to check whether it # contains cpassword\r\nattribute and display it. foreach ( $file in $impactedXmls ) { $fileFullPath = $file.FullName\r\n# Set GPP category. If file is located under Machine folder in SYSVOL # the setting is defined under computer\r\nconfiguration otherwise the # setting is a to user configuration if ( $fileFullPath.Contains(\"Machine\") ) { $category =\r\n\"Computer Configuration\" } elseif ( $fileFullPath.Contains(\"User\") ) { $category = \"User Configuration\" } else { $category\r\n= \"Unknown\" } # Obtain file content as XML try { [xml]$xmlFile = get-content $fileFullPath -ErrorAction Continue } catch\r\n[Exception]{ Write-Host $_.Exception.Message } if ($xmlFile -eq $null) { continue } switch ( $file.BaseName ) { Groups {\r\n$gppWithCpassword = $xmlFile.SelectNodes(\"Groups/User\") | where-Object {\r\n[String]::IsNullOrEmpty($_.Properties.cpassword) -eq $false } $preferenceType = \"Local Users\" } ScheduledTasks {\r\n$gppWithCpassword = $xmlFile.SelectNodes(\"ScheduledTasks/*\") | where-Object {\r\n[String]::IsNullOrEmpty($_.Properties.cpassword) -eq $false } $preferenceType = \"Scheduled Tasks\" } DataSources {\r\n$gppWithCpassword = $xmlFile.SelectNodes(\"DataSources/DataSource\") | where-Object {\r\n[String]::IsNullOrEmpty($_.Properties.cpassword) -eq $false } $preferenceType = \"Data sources\" } Drives {\r\n$gppWithCpassword = $xmlFile.SelectNodes(\"Drives/Drive\") | where-Object {\r\n[String]::IsNullOrEmpty($_.Properties.cpassword) -eq $false } $preferenceType = \"Drive Maps\" } Services {\r\n$gppWithCpassword = $xmlFile.SelectNodes(\"NTServices/NTService\") | where-Object {\r\n[String]::IsNullOrEmpty($_.Properties.cpassword) -eq $false } $preferenceType = \"Services\" } default { # clear\r\ngppWithCpassword and preferenceType for next item. try { Clear-Variable -Name gppWithCpassword -ErrorAction\r\nSilentlyContinue Clear-Variable -Name preferenceType -ErrorAction SilentlyContinue } catch [Exception]{} } } if\r\n($gppWithCpassword -ne $null) { # Build GPO name from GUID extracted from filePath $guidRegex = [regex]\"\\{(.*)\\}\"\r\n$match = $guidRegex.match($fileFullPath) if ($match.Success) { $gpoGuid = $match.groups[1].value $gpoName =\r\n$gpoGuid } else { $gpoName = \"Unknown\" } if($isGPModuleAvailable -eq $true) { try { $gpoInfo = Get-GPO -Guid\r\n$gpoGuid -ErrorAction Continue $gpoName = $gpoInfo.DisplayName } catch [Exception] { Write-Host\r\n$_.Exception.Message } } # display prefrences that contain cpassword foreach ( $gpp in $gppWithCpassword ) { if (\r\n$preferenceType -eq \"Drive Maps\" ) { $prefLocation = $category + $driveMapPath + $preferenceType } else {\r\n$prefLocation = $category + $commonPath + $preferenceType } $obj = New-Object -typeName PSObject $obj | Add-Member –membertype NoteProperty –name GPOName –value ($gpoName) –passthru | Add-Member -MemberType\r\nNoteProperty -name Preference -value ($gpp.Name) -passthru | Add-Member -MemberType NoteProperty -name Path -\r\nvalue ($prefLocation) Write-Output $obj } } # end if $gppWithCpassword } # end foreach $file} # end functions Enum-PoliciesWithCpassword#-----------------------------------------------------------------------------------# Check whether Path is valid.\r\nEnumerate all settings that contain cpassword. #-----------------------------------------------------------------------------------if\r\n(Test-Path $Path ){ Enum-SettingsWithCpassword $Path}else{ Write-Warning \"No such directory: $Path\"}\r\nExample usage (assumes that the system drive is C)\r\n.\\Get-SettingsWithCPassword.ps1 –path “C:\\Windows\\SYSVOL\\domain” | Format-List Note Be aware that you can also\r\ntarget any backup GPO for the path instead of the domain.\r\nThe detection script generates a list that resembles the following:\r\nFor longer lists, consider saving the output to a file:\r\n.\\Get-SettingsWithCPassword.ps1 –path “C:\\Windows\\SYSVOL\\domain” | ConvertTo-Html \u003e gpps.html\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 12 of 14\n\nRemoving CPassword preferences\r\nIn order to remove the preferences that contain CPassword data, we suggest that you use Group Policy Management\r\nConsole (GPMC) on the domain controller or from a client that has Remote Server Administration Tools installed. You can\r\nremove any preference in five steps on these consoles. To do this, follow these steps:\r\n1. In GPMC, open the preference that contains CPassword data.\r\n2. Change the action to Delete or Disable, as applicable to the preference.\r\n3. Click OK to save your changes.\r\n4. Wait for one or two Group Policy refresh cycles to allow changes to propagate to clients.\r\n5. After changes are applied on all clients, delete the preference.\r\n6. Repeat steps 1 through 5 as needed to clean your whole environment. When the detection script returns zero results,\r\nyou are finished.\r\nFile name SHA1 hash SHA256 hash\r\nWindows6.0-\r\nKB2928120-\r\nia64.msu\r\nB2A74305CB56191774BFCF9FCDEAA983B26DC9A6 DCE8C0F9CEB97DBF1F7B9BAF76458B3770EF01C0EDC581621B\r\nWindows6.0-\r\nKB2928120-\r\nx64.msu\r\n386457497682A2FB80BC93346D85A9C1BC38FBF7 1AF67EB12614F37F4AC327E7B5767AFA085FE676F6E81F0CED95\r\nWindows6.0-\r\nKB2928120-\r\nx86.msu\r\n42FF283781CEC9CE34EBF459CA1EFE011D5132C3 016D7E9DBBC5E487E397BE0147B590CFBBB5E83795B997894870\r\nWindows6.1-\r\nKB2928120-\r\nia64.msu\r\n5C2196832EC94B99AAF9B074D3938525B7219690 9958FA58134F55487521243AD9740BEE0AC210AC290D45C8322E\r\nWindows6.1-\r\nKB2928120-\r\nx64.msu\r\nEA5332F4E289DC799611EAB8E3EE2E86B7880A4B 417A2BA34F8FD367556812197E2395ED40D8B394F9224CDCBE8A\r\nWindows6.1-\r\nKB2928120-\r\nx86.msu\r\n7B7B6EE24CD8BE1AB3479F9E1CF9C98982C8BAB1 603206D44815EF2DC262016ED13D6569BE13D06E2C6029FB2262\r\nWindows8-\r\nRT-KB2928120-\r\nx64.msu\r\nE18FC05B4CCA0E195E62FF0AE534BA39511A8593 FCAED97BF1D61F60802D397350380FADED71AED64435D3E9EA\r\nWindows8-\r\nRT-KB2928120-\r\nx86.msu\r\nA5DFB34F3B9EAD9FA78C67DFC7ACACFA2FBEAC0B 7F00A72D8A15EB2CA70F7146A8014E39A71CFF5E39596F379AC\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 13 of 14\n\nFile name SHA1 hash SHA256 hash\r\nWindows8.1-\r\nKB2928120-\r\nx64.msu\r\nA07FF14EED24F3241D508C50E869540915134BB4 6641B1A9C95A7E4F0D5A247B9F488887AC94550B7F1D7B1198D\r\nWindows8.1-\r\nKB2928120-\r\nx86.msu\r\nDE84667EC79CBA2006892452660EB99580D27306 468EE4FA3A22DDE61D85FD3A9D0583F504105DF2F8256539051B\r\nWindows8.1-\r\nKB2961899-\r\nx64.msu\r\n10BAE807DB158978BCD5D8A7862BC6B3EF20038B EC26618E23D9278FC1F02CA1F13BB289E1C6C4E0C8DA5D22E1D\r\nWindows8.1-\r\nKB2961899-\r\nx86.msu\r\n230C64447CC6E4AB3AD7B4D4655B8D8CEFBFBE98 E3FAD567AB6CA616E42873D3623A777185BE061232B952938A88\r\nSource: http://support.microsoft.com/kb/2962486\r\nhttp://support.microsoft.com/kb/2962486\r\nPage 14 of 14",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"http://support.microsoft.com/kb/2962486"
	],
	"report_names": [
		"2962486"
	],
	"threat_actors": [],
	"ts_created_at": 1775434432,
	"ts_updated_at": 1775826708,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/becd011c00d25d50f50a3b6cb99360647475e0e5.pdf",
		"text": "https://archive.orkl.eu/becd011c00d25d50f50a3b6cb99360647475e0e5.txt",
		"img": "https://archive.orkl.eu/becd011c00d25d50f50a3b6cb99360647475e0e5.jpg"
	}
}