a default installation of Microsoft Exchange within an AD env (with bo split-administration model) opens up many attack vectors
exchange is granted considerable privileges
Exchange Windows Permissions is not listed as a protected group, but members are granted the ability to write a DACL to the domain object.
This can allow us to give users DCSync privileges
An attacker can add accounts to this group by leveraging a DACL misconfiguration (possible) or by leveraging a compromised account that is a member of the Account Operators group
https://github.com/gdedrouas/Exchange-AD-Privesc
Exchange group Organization Management - powerful
can access mailbox of all domain users
sysadmins could be a part of this group
full control of the OU called Microsoft Exchange Security Groups, which contains the group Exchange Windows Permissions.
If we can compromise an Exchange server, this will often lead to Domain Admin privileges. Additionally, dumping credentials in memory from an Exchange server will produce 10s if not 100s of cleartext credentials or NTLM hashes. This is often due to users logging in to Outlook Web Access (OWA) and Exchange caching their credentials in memory after a successful login.
PrivExchange
PushSubscription feature of Exchange
Allows any domain user with a mailbox to force the Exchange server to authenticate to any host provided by the client over HTTP
PrinterBug
The spooler service runs as SYSTEM and is installed by default in Windows servers running Desktop Experience. This attack can be leveraged to relay to LDAP and grant your attacker account DCSync privileges to retrieve all password hashes from AD.
This flaw can be used to compromise a host in another forest that has Unconstrained Delegation enabled, such as a domain controller. It can help us to attack across forest trusts once we have compromised one forest.
Patched in 2014 - https://support.microsoft.com/en-us/topic/ms14-025-vulnerability-in-group-policy-preferences-could-allow-elevation-of-privilege-may-13-2014-60734e15-af79-26ca-ea53-8cd617073c30
The patch does not remove existing Groups.xml files with passwords from SYSVOL.
Decrypting the password found in Groups.xml from SYSVOL