HackTricks
Search…
Pentesting
Powered By GitBook
Kerberos Authentication
This information was extracted from the post: https://www.tarlogic.com/en/blog/how-kerberos-works/

Kerberos (I): How does Kerberos work? – Theory

20 - MAR - 2019 - ELOY PÉREZ
The objective of this series of posts is to clarify how Kerberos works, more than just introduce the attacks. This due to the fact that in many occasions it is not clear why some techniques works or not. Having this knowledge allows to know when to use any of those attacks in a pentest.
Therefore, after a long journey of diving into the documentation and several posts about the topic, we’ve tried to write in this post all the important details which an auditor should know in order to understand how take advantage of Kerberos protocol.
In this first post only basic functionality will be discussed. In later posts it will see how perform the attacks and how the more complex aspects works, as delegation.
If you have any doubt about the topic which it is not well explained, do not be afraid on leave a comment or question about it. Now, onto the topic.

What is Kerberos?

Firstly, Kerberos is an authentication protocol, not authorization. In other words, it allows to identify each user, who provides a secret password, however, it does not validates to which resources or services can this user access.
Kerberos is used in Active Directory. In this platform, Kerberos provides information about the privileges of each user, but it is responsability of each service to determine if the user has access to its resources.

Kerberos items

In this section several components of Kerberos environment will be studied.
Transport layer
Kerberos uses either UDP or TCP as transport protocol, which sends data in cleartext. Due to this Kerberos is responsible for providing encryption.
Ports used by Kerberos are UDP/88 and TCP/88, which should be listen in KDC (explained in next section).
Agents
Several agents work together to provide authentication in Kerberos. These are the following:
    Client or user who wants to access to the service.
    AP (Application Server) which offers the service required by the user.
    KDC (Key Distribution Center), the main service of Kerberos, responsible of issuing the tickets, installed on the DC (Domain Controller). It is supported by the AS (Authentication Service), which issues the TGTs.
Encryption keys
There are several structures handled by Kerberos, as tickets. Many of those structures are encrypted or signed in order to prevent being tampered by third parties. These keys are the following:
    KDC or krbtgt key which is derivate from krbtgt account NTLM hash.
    User key which is derivate from user NTLM hash.
    Service key which is derivate from the NTLM hash of service owner, which can be an user or computer account.
    Session key which is negotiated between the user and KDC.
    Service session key to be use between user and service.
Tickets
The main structures handled by Kerberos are the tickets. These tickets are delivered to the users in order to be used by them to perform several actions in the Kerberos realm. There are 2 types:
    The TGS (Ticket Granting Service) is the ticket which user can use to authenticate against a service. It is encrypted with the service key.
    The TGT (Ticket Granting Ticket) is the ticket presented to the KDC to request for TGSs. It is encrypted with the KDC key.
PAC
The PAC (Privilege Attribute Certificate) is an structure included in almost every ticket. This structure contains the privileges of the user and it is signed with the KDC key.
It is possible to services to verify the PAC by comunicating with the KDC, although this does not happens often. Nevertheless, the PAC verification consists of checking only its signature, without inspecting if privileges inside of PAC are correct.
Furthermore, a client can avoid the inclusion of the PAC inside the ticket by specifying it in KERB-PA-PAC-REQUEST field of ticket request.
Messages
Kerberos uses differents kinds of messages. The most interesting are the following:
    KRB_AS_REQ: Used to request the TGT to KDC.
    KRB_AS_REP: Used to deliver the TGT by KDC.
    KRB_TGS_REQ: Used to request the TGS to KDC, using the TGT.
    KRB_TGS_REP: Used to deliver the TGS by KDC.
    KRB_AP_REQ: Used to authenticate a user against a service, using the TGS.
    KRB_AP_REP: (Optional) Used by service to identify itself against the user.
    KRB_ERROR: Message to comunicate error conditions.
Additionally, even if it is not part of Kerberos, but NRPC, the AP optionally could use the KERB_VERIFY_PAC_REQUEST message to send to KDC the signature of PAC, and verify if it is correct.
Below is shown a summary of message sequency to perform authentication
Kerberos messages summary

Authentication process

In this section, the sequency of messages to perform authentication will be studied, starting from a user without tickets, up to being authenticated against the desired service.
KRB_AS_REQ
Firstly, user must get a TGT from KDC. To achieve this, a KRB_AS_REQ must be sent:
KRB_AS_REQ schema message
KRB_AS_REQ has, among others, the following fields:
    A encrypted timestamp with client key, to authenticate user and prevent replay attacks
    Username of authenticated user
    The service SPN asociated with krbtgt account
    A Nonce generated by the user
Note: the encrypted timestamp is only necessary if user requires preauthentication, which is common, except if DONT_REQ_PREAUTH flag is set in user account.
KRB_AS_REP
After receiving the request, the KDC verifies the user identity by decrypting the timestamp. If the message is correct, then it must respond with a KRB_AS_REP:
KRB_AS_REP schema message
KRB_AS_REP includes the next information:
    Username
    TGT, which includes:
      Username
      Session key
      Expiration date of TGT
      PAC with user privileges, signed by KDC
    Some encrypted data with user key, which includes:
      Session key
      Expiration date of TGT
      User nonce, to prevent replay attacks
Once finished, user already has the TGT, which can be used to request TGSs, and afterwards access to the services.
KRB_TGS_REQ
In order to request a TGS, a KRB_TGS_REQ message must be sent to KDC:
KRB_TGS_REQ schema message
KRB_TGS_REQ includes:
    Encrypted data with session key:
      Username
      Timestamp
    TGT
    SPN of requested service
    Nonce generated by user
KRB_TGS_REP
After receiving the KRB_TGS_REQ message, the KDC returns a TGS inside of KRB_TGS_REP:
KRB_TGS_REP schema message
KRB_TGS_REP includes:
    Username
    TGS, which contains:
      Service session key
      Username
      Expiration date of TGS
      PAC with user privileges, signed by KDC
    Encrypted data with session key:
      Service session key
      Expiration date of TGS
      User nonce, to prevent replay attacks
KRB_AP_REQ
To finish, if everything went well, the user already has a valid TGS to interact with service. In order to use it, user must send to the AP a KRB_AP_REQ message:
KRB_AP_REQ schema message
KRB_AP_REQ includes:
    TGS
    Encrypted data with service session key:
      Username
      Timestamp, to avoid replay attacks
After that, if user privileges are rigth, this can access to service. If is the case, which not usually happens, the AP will verify the PAC against the KDC. And also, if mutual authentication is needed it will respond to user with a KRB_AP_REP message.

References

Last modified 1yr ago