Vigilant (Chain)

This is not a writeup, just my notes about the machine.

Operating System: Microsoft Windows Server 2022 Standard

Chain: True (2 Machines)

Credentials

Username
Password
Method
Scope

svc_auditreporter

DeVeLoPeR712

Extracted from .dll

Domain user

Pamela.Clark

Vigilant@Tech2024

Extracted from decrypted PDF

Domain user

Alex.Powell

Vigilant_Market2024

Extracted from decrypted PDF

Domain user

Edwin.Dixon

Vigilant_Finance$

Extracted from decrypted PDF

Domain user

Daniel.Washington

Vigilant&Strategy!

Extracted from decrypted PDF

Domain user

✅ Valid Usernames

🔑 Passwords list

Information Gathering

Nmap Scan

Service enumeration

vigilant.vl

DNS

  • Not vulnerable to DNS Zone transfer

SMB (enum4linux-ng)

  • Domain SID: S-1-5-21-2615182196-3196294898-3079774137

  • Root/parent domain

  • SMB signing: true (Not vulnerable to NTLM Relay attacks)

  • NetBIOS computer name: DC

  • NetBIOS domain name: VIGILANT

  • Domain: vigilant.vl

  • FQDN: DC.vigilant.vl

  • Server allows null session authentication

  • server allows guest session authentication (useful for enumeation)

HTTP: 5601

Elastic instance

10.10.145.214

HTTP:80

Compromise SRV

Initial Foothold on SRV

Discovering a sensitive files on SMB

Valuable file: Password_Strength_Report_encrypted.pdf

Discovering a domain user credentials in the ADAudit.dll

During the enumeration the tester found ADAudit.dll which containing svc_auditreporter's plaintext credentials.

Credentials: svc_auditreporter : DeVeLoPeR712

Decrypting pdf

Authenticating on Elastic

The tester authenticate on Elastic using Pamela.clark credentials

Discovering Pamela.clark is a superuser

Getting a reverse shell using

The tester configured a monitor in http://10.10.224.229:5601/app/synthetics/add-monitorarrow-up-right

Creating a synthetics project

Creating a malicious monitor

The tester modified journeys/example.journey.ts as follows:

Compromise SRV via Docker Breakout

Discovering docker.sock was exposed

Escaping to the container via Docker breakout using SOCK method

Compromising Domain Controller

Initial foothold on DC

Discovering cache credentials

Hash found: $6$CI3DH6Ihe8SOgnFz$rzgx1xAQK4kz8YoMqQ90LrDmQs9nJEx9CujSE6BWInbeog6Uf1k9vd.Ub1V23KD2DzsK4RIWpWz/5Iw.RcQhp0

Cracking hash discovered hash

Changing Gabriel.Steward's password

Compromise domain controller via ESC13

Discovering a vulnerable template to ESC13

Requirements

  1. The certificate template specifies an issuance policy (msPKI-Certificate-Policy )

  1. That issuance policy is linked to a privileged group (msDS-OIDToGroupLink)

  1. The linked group meets two conditions:

    1. It is empty (no members)

    2. It has universal scope (i.e., forest-wide group like Enterprise Admins, Schema Admins, or any custom universal group)

universal scope
  1. The certificate template allows Client Authentication

  1. 🎉 The compromised user/computer can enroll in the certificate template.

Abusing ESC13 using Certipy

circle-exclamation

Last updated