Skip to content

Local Administrator Check

Determines whether the configured Standard User has local administrator access on any domain-joined systems, including Domain Controllers.

ad-kit check local-admin

Prerequisite

Requires a valid Standard User account (authenticated).

Commands run

ad-kit first builds a host list with NetExec:

nxc ldap <dc_ip> -u <username> -p <password> --computers

Then it attempts an SMB login with the Standard User against each host:

nxc smb <hosts_file> -u <username> -p <password>

What it checks

ad-kit attempts an SMB login with the Standard User against each host and detects success (Pwn3d!). Results are split into member systems and Domain Controllers.

How it works

Local administrator access grants control of a system: installing software, modifying services, reading sensitive local data, and interacting with other sessions. An account with local admin on one host can be used to harvest credentials and move further through the environment. Administrative access to a Domain Controller is far more significant because it provides direct access to Active Directory data.

Why it matters

Over-provisioned local administration is a common enabler of privilege escalation and lateral movement. Restricting it to dedicated administrative accounts reduces the impact of a compromised Standard User.

Findings

Finding ID Title
LA-001 Standard User Has Local Administrator Access
LA-002 Standard User Has Administrative Access to Domain Controller

Tooling

References