SYSVOL & Group Policy Preferences
Windows systems come with a built-in Administrator (with an RID of 500) that most organizations want to change the password of. This can be achieved in multiple ways but there is one that is to be avoided: setting the built-in Administrator's password through Group Policies.
The first problem is that the password is set to be the same for every (set of) machine(s) the Group Policy applies to. If the attacker finds the admin's hash or password, he can gain administrative access to all (or set of) machines. by default, knowing the built-in Administrator's hash (RID 500) allows for powerful attacks. all Group Policies are stored in the Domain Controllers' SYSVOL share. All domain users have read access to it. This means all domain users can read the encrypted password set in Group Policy Preferences, and since Microsoft published the encryption key around 2012, the password can be decrypted.
From UNIX-like systems, this python script in the impacket examples can be used to remotely parse .xml files and loot for passwords
Alternatively, searching for passwords can be done manually (or with Metasploit's smb_enum_gpp module), however it requires mounting the SYSVOL share, which can't be done through a docker environment unless it's run with privileged rights. Tools like pypykatz and gpp-decrypt can then be used to decrypt the matches.
From Windows systems, the GPP password can only be recovered from an authenticated (i.e. domain user) context. βpowersploit's get-gpppassword
searches a Domain Controller's SYSVOL share Groups.xml, Services.xml, Scheduledtasks.xml, DataSources.xml, Printers.xml and Drives.xml files and returns plaintext passwords
This can also be achieved without tools, by "manually" looking for the cpassword string in xml files and by then manually decrypting the matches
The decryption process is as follows
Last updated