Silver Ticket
Last updated
Last updated
On the last step of the process when the client sends a TGS to the service that is where we can send a forged TGS and get access directly to the service and get a service ticket using this method.
downside of this attack is at unlike golden ticket which gives us access to everything.
A silver ticket will only allow us access to a particular service or all the services that are running with the same service account.
Another disadvantage of this attack is if the service account is a machine account or a user account. If the password of the account changes this attack will fail. Since we wont have the correct hash of the user/machine account usually it changes within 30 days for machines.
We would generally target these services when it comes to performing a silver ticket attack. CIFS (file system), HOST ( can schedule tasks ), RPCSS Host (runs wmi), WSman/http (ps remoting) all of these use the machine account as there service account.
If an attacker can gain admin rights to the computer (to gain debug access) or be able to run code as local System, the attacker can dump the AD computer account password hash from the system using Mimikatz (the NTLM password hash is used to encrypt RC4 Kerberos tickets)
Target – This is the host, which can be copied from the SPN value.
/domain : domain name
/sid: domain SID value
/target: target service SPN
/service: service name
/user: username to create ticket for
/rc4: NTLM hash, will use
/id , /groups : these are to specify user id and group but this is optional
/endin : specify ticket lifetime in minutes (default 10 years)
/ptt : stands for pass the ticket it will load the ticket in memory. If we want to extract ticket on disk we can use /ticket option instead.
By issuing a klist command you can see that we now have the ticket for sql service.
more attack scenarios with silver tickets