Domain 4PrivEsc & Password AttacksCORE

System Information Gathering

Complete guide to gathering system information on Windows targets including OS version, patches, architecture, network config, and installed software to identify exploit vectors.

Domain: Domain 4: Privilege Escalation & Password Attacks•Updated: 2026-09-01
#enumeration#systeminfo#reconnaissance#os-version#patches

System Information Gathering

Why System Info Gathering Is Critical

System information gathering is the bridge between enumeration and exploitation. Every kernel exploit, every service vulnerability, every misconfiguration has specific prerequisites. Without knowing the exact OS version, build number, and installed patches, you cannot determine which exploits apply.

The core workflow:

  1. Gather system information (systeminfo, wmic, PowerShell)
  2. Identify the OS version and build number
  3. Check installed patches/hotfixes
  4. Cross-reference with known exploits (ExploitSuggester, manual research)
  5. Select and execute the appropriate attack

Exam Tip: Save the output of systeminfo to a file. You will need it for ExploitSuggester.py. Always run this early in your engagement.

systeminfo > C:\temp\systeminfo.txt 2>&1
wmic qfe get Caption,Description,HotFixID,InstalledOn > C:\temp\hotfixes.txt 2>&1

Core Commands — Detailed Breakdown

systeminfo — The Most Important Command

systeminfo

This single command provides the most comprehensive system overview. Let’s analyze every field:

Full example output:

Host Name:                 WIN-SERVER2019
OS Name:                   Microsoft Windows Server 2019 Standard
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00256-70000-00000-AA003
Original Install Date:     8/10/2025, 3:15:42 AM
System Boot Time:          8/20/2025, 10:12:33 AM
System Manufacturer:       VMware, Inc.
System Model:              VMware Virtual Platform
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~2494 Mhz
BIOS Version:              Phoenix Technologies LTD 6.00, 2/3/2022
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
Total Physical Memory:     16,384 MB
Available Physical Memory: 12,456 MB
Virtual Memory: Max Size:  17,344 MB
Virtual Memory: Available: 14,200 MB
Virtual Memory: In Use:    3,144 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              N/A
Hotfix(s):                 1 Hotfix(s) Installed.
                           [01]: KB5004948
Network Card(s):           1 NIC(s) Installed.
                           [01]: Intel(R) 82574L Gigabit Network Connection
                                 Connection Name: Ethernet0
                                 DHCP Enabled:    Yes
                                 IP address(es)
                                 [01]: 10.10.10.100
                                 [02]: fe80::d5c8:a8ff:fe34:5678

Field-by-Field Analysis

Field Why It Matters Privesc Relevance
OS Name Identifies the Windows edition Determines available exploits (Server vs. Client have different attack surfaces)
OS Version / Build Critical — exact build number Directly maps to known kernel exploits. Build 17763 = Windows Server 2019 RTM
System Type x64 or x86 Determines which exploit binary to use (32-bit vs 64-bit)
System Manufacturer Hardware/VM vendor VMware/VirtualBox = VM detection. May indicate specific VM tools vulnerabilities
System Model Specific hardware model VM model confirms virtualization
Processor CPU architecture and speed Confirms x64, helps with exploit compatibility
BIOS Version Firmware version VM BIOS versions can confirm virtualization type
Domain WORKGROUP or domain name Domain = Active Directory attacks available. WORKGROUP = local-only
Hotfix(s) Installed patches Critical — missing patches = potential exploits. Feed to ExploitSuggester
Network Card(s) NIC details and IPs Network topology, pivot planning, lateral movement targets
Total Physical Memory RAM amount Helps identify system capabilities

OS Version to Build Number Reference Table

OS Name Version Build Number(s) Common Exploits
Windows XP 5.1 2600 MS08-067, various kernel exploits
Windows Server 2003 5.2 3790 MS08-067, various kernel exploits
Windows 7 6.1 7600, 7601 (SP1) MS16-032, MS17-010, various
Windows 8 6.2 9200 MS16-032, various
Windows 8.1 6.3 9600 MS16-032, various
Windows 10 1507 10.0 10240 MS16-032, various
Windows 10 1511 10.0 10586 Various
Windows 10 1607 10.0 14393 Various
Windows 10 1703 10.0 15063 Various
Windows 10 1709 10.0 16299 Various
Windows 10 1803 10.0 17134 Various
Windows 10 1809 10.0 17763 PrintNightmare, various
Windows 10 1903 10.0 18362 Various
Windows 10 1909 10.0 18363 Various
Windows 10 2004 10.0 19041 Various
Windows 10 20H2 10.0 19042 Various
Windows 10 21H1 10.0 19043 Various
Windows 10 21H2 10.0 19044 Various
Windows 10 22H2 10.0 19045 Various
Windows 11 21H2 10.0 22000 Various
Windows 11 22H2 10.0 22621 Various
Windows Server 2008 6.0 6002 (SP2) MS16-032, MS17-010
Windows Server 2008 R2 6.1 7601 MS16-032, MS17-010
Windows Server 2012 6.2 9200 Various
Windows Server 2012 R2 6.3 9600 Various
Windows Server 2016 10.0 14393 Various
Windows Server 2019 10.0 17763 PrintNightmare, various
Windows Server 2022 10.0 20348 Various

Exam Tip: The build number is the most important piece of data. 10.0.17763 means Windows 10 1809 or Server 2019. Use this to look up exploits.


ver — Quick OS Version Check

ver

Output:

Microsoft Windows [Version 10.0.17763.4737]

This gives you the OS version and build in one line. Quick and reliable. The number after the third dot (.4737) is the revision/patch level.


wmic os get osarchitecture — System Architecture

wmic os get osarchitecture

Output:

OSArchitecture
64-bit

Why it matters:

  • Determines whether you need 32-bit or 64-bit exploit binaries
  • Affects which payloads to generate with msfvenom
  • Some exploits only work on specific architectures

Alternative commands:

echo %PROCESSOR_ARCHITECTURE%
# Output: AMD64

wmic ComputerSystem get SystemType
# Output: x64-based PC

wmic qfe — Installed Hotfixes/Patches

wmic qfe get Caption,Description,HotFixID,InstalledOn

Output:

Caption                  Description        HotFixID    InstalledOn
Windows Update           Update           KB5004948   8/15/2025
Windows Update           Security Update  KB5005080   8/18/2025

Why this matters:

  • Each HotFixID (KB number) represents an installed patch
  • Missing patches = potential exploits
  • Feed this data to ExploitSuggester.py to find applicable exploits
  • Cross-reference KB numbers with Microsoft’s security bulletins

Alternative (PowerShell):

Get-HotFix | Select-Object HotFixID, Description, InstalledOn, InstalledBy | Format-Table -AutoSize

hostname — System Name

hostname

Output:

WIN-SERVER2019

Useful for:

  • Identifying the target in your notes
  • Referencing the system in lateral movement commands
  • Some exploits use the hostname in their output

Network Enumeration

ipconfig /all — Full Network Configuration

ipconfig /all

Output:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : WIN-SERVER2019
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-50-56-34-56-78
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.10.10.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 8/20/2025 10:12:35 AM
   Lease Expires . . . . . . . . . . : 8/21/2025 10:12:35 AM
   Default Gateway . . . . . . . . . : 10.10.10.1
   DHCP Server . . . . . . . . . . . : 10.10.10.1
   DNS Servers . . . . . . . . . . . : 10.10.10.1
                                       127.0.0.53
   NetBIOS over Tcpip. . . . . . . . : Enabled

Privesc relevance:

  • Multiple NICs/IPs: May indicate multi-homed systems with access to internal networks (pivot opportunities)
  • DNS Servers: Internal DNS servers may reveal domain infrastructure
  • Default Gateway: Confirms network segmentation
  • DHCP vs Static: Static IPs often indicate servers or critical infrastructure

arp -a — ARP Table

arp -a

Output:

Interface: 10.10.10.100 --- 0x9
  Internet Address      Physical Address      Type
  10.10.10.1            00-50-56-c0-00-08     dynamic
  10.10.10.5            00-50-56-34-12-34     dynamic
  10.10.10.255          ff-ff-ff-ff-ff-ff     static
  10.10.10.255          ff-ff-ff-ff-ff-ff     static

Privesc relevance:

  • Shows other hosts on the same subnet
  • Identifies potential lateral movement targets
  • Gateway MAC confirms network topology

route print — Routing Table

route print

Output:

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      10.10.10.1      10.10.10.100     25
     10.10.10.0    255.255.255.0     10.10.10.100     10.10.10.100    281
     10.10.10.100  255.255.255.255         On-link    10.10.10.100    281
     10.10.10.255  255.255.255.255         On-link    10.10.10.100    281
     10.10.10.255  255.255.255.255         On-link    10.10.10.100    281
        127.0.0.0        255.0.0.0         On-link    127.0.0.1       331
        127.0.0.1  255.255.255.255         On-link    127.0.0.1       331
  127.255.255.255  255.255.255.255         On-link    127.0.0.1       331
     172.16.0.0      255.240.0.0     10.10.10.1     10.10.10.100    281
        224.0.0.0        240.0.0.0         On-link    10.10.10.100    281
        224.0.0.0        240.0.0.0         On-link    127.0.0.1       331
  255.255.255.255  255.255.255.255         On-link    10.10.10.100    281
  255.255.255.255  255.255.255.255         On-link    127.0.0.1       331
===========================================================================

Privesc relevance:

  • Multiple network destinations: Route to 172.16.0.0/12 indicates access to an internal network — potential pivot target
  • Default gateway: Confirms network exit point
  • On-link routes: Directly connected networks

netstat -ano — Active Connections

netstat -ano

Output:

Active Connections

Proto  Local Address          Foreign Address        State           PID
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       448
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       448
TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING       4
TCP    0.0.0.0:49668          0.0.0.0:0              LISTENING       1200
TCP    10.10.10.100:49670     10.10.14.5:4444        ESTABLISHED     3456
TCP    10.10.10.100:50123     10.10.10.1:53          TIME_WAIT       0
UDP    0.0.0.0:137            *:*                                    4
UDP    0.0.0.0:138            *:*                                    4

Privesc relevance:

  • Listening ports: Identify running services (3389=RDP, 445=SMB, 135=RPC, 5985=WinRM)
  • ESTABLISHED connections: Active sessions to other hosts — lateral movement evidence
  • PID column: Correlate with tasklist to identify which process owns each connection
  • Unexpected ports: Non-standard services may have vulnerabilities

Correlate with processes:

tasklist /FI "PID eq 3456"
# Shows which process is making the outbound connection

netsh advfirewall — Firewall Configuration

# Show all firewall rules
netsh advfirewall firewall show rule name=all

# Show current profile state
netsh advfirewall show allprofiles

# Show current rules summary
netsh advfirewall firewall show rule name=all verbose

Output (profile state):

Domain Profile
--------------
State ON
Inbound Connections Block
Outbound Connections Allow
...

Private Profile
---------------
State ON
Inbound Connections Block
Outbound Connections Allow
...

Public Profile
--------------
State OFF
Inbound Connections Allow
Outbound Connections Allow

Privesc relevance:

  • Firewall disabled: All ports accessible — more attack surface
  • Allowed inbound rules: May reveal services accessible from outside
  • Allowed outbound rules: May restrict your ability to callback to attacker machine

PowerShell Deep Enumeration

Get-CimInstance — WMI via PowerShell

CIM (Common Information Model) is the modern replacement for WMI. Get-CimInstance provides structured access to system information.

OS Details

Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber, OSArchitecture, InstallDate, LastBootUpTime, TotalVisibleMemorySize | Format-List

Output:

Caption              : Microsoft Windows Server 2019 Standard
Version              : 10.0.17763
BuildNumber          : 17763
OSArchitecture       : 64-bit
InstallDate          : 20250810031542.000000-000
LastBootUpTime       : 20250820101233.000000-000
TotalVisibleMemorySize : 16777216

Hotfixes

Get-HotFix | Select-Object HotFixID, Description, InstalledOn, InstalledBy | Format-Table -AutoSize

Process Enumeration

Get-Process | Select-Object Name, Id, Path, Company, StartTime | Sort-Object Path | Format-Table -AutoSize

Why process enumeration matters:

  • Running processes reveal installed software
  • Processes running as SYSTEM are potential targets for token theft
  • Unusual processes may indicate security software (EDR, AV) that could block exploits
  • Processes with writable paths are DLL hijacking targets

Installed Software (Registry Method — Faster)

# 64-bit uninstall key
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" |
    Select-Object DisplayName, DisplayVersion, Publisher, InstallDate |
    Where-Object { $_.DisplayName } |
    Sort-Object DisplayName |
    Format-Table -AutoSize

# 32-bit on 64-bit system
Get-ItemProperty "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" |
    Select-Object DisplayName, DisplayVersion, Publisher, InstallDate |
    Where-Object { $_.DisplayName } |
    Sort-Object DisplayName |
    Format-Table -AutoSize

Why installed software matters:

  • Outdated software with known vulnerabilities = exploitation targets
  • Development tools (Python, Node.js, compilers) = can compile payloads locally
  • Database software = potential credential stores
  • Remote management tools = alternative access vectors

Installed Software (Win32_Product Method — Slower but Complete)

Get-CimInstance -ClassName Win32_Product | Select-Object Name, Version, Vendor | Format-Table -AutoSize

Warning: This method triggers Windows Installer consistency checks and can be very slow on systems with many installed packages. Use the registry method above for speed.


WMIC Deep Enumeration

WMIC (Windows Management Instrumentation Command-line) provides access to WMI data via command line. Note: WMIC is deprecated in Windows 11 24H2 but still works on most OSCP targets.

Services

wmic service list brief

Output (truncated):

Caption                          Name
Application Experience           AepService
Application Identity             ApplicationIdentity
Application Information          Appinfo
...

Detailed service info:

wmic service get name,displayname,pathname,startmode | findstr /i /v "C:\Windows\\"

This filters out Windows system services and shows third-party services — the most likely to have misconfigurations.

Startup Programs

wmic startup get caption,command

Output:

Caption                        Command
uTorrent                      C:\Program Files\uTorrent\uTorrent.exe
Adobe Reader Update           "C:\Program Files\Adobe\Reader AC\Reader\Core\Updater\AdobeUpdater.exe"

Privesc relevance: Startup programs that run with elevated privileges or have writable paths are attack vectors.

BIOS and System Info

wmic bios get smbiosbiosversion,manufacturer,name,releasedate

Output:

Manufacturer            Name                                Releasedate        SMBIOSBIOSVersion
Phoenix Technologies LTD PhoenixBIOS 4.0 Release 1.0        02/03/22           6.00

Privesc relevance: Confirms VM vs physical. VM BIOS versions can sometimes indicate specific virtualization platforms with known vulnerabilities.

Disk Information

wmic logicaldisk get caption,description,providername,size,freespace

Output:

Caption  Description    ProviderName  Size         FreeSpace
C:       Fixed Disk                    53687091200  21474836480
D:       CD-ROM Drive  \\.\CDROM0

Privesc relevance:

  • Available drives = places to store payloads
  • CD-ROM drives = may contain installation media with tools
  • Disk space = need room for large exploit binaries

Network Adapters

wmic nicconfig where IPEnabled=True get Caption,IPAddress,MACAddress,DefaultIPGateway,IPSubnet

Output:

Caption                                  IPAddress        MACAddress       DefaultIPGateway  IPSubnet
Intel(R) 82574L Gigabit Network...       {10.10.10.100}   00:50:56:34:56:78  {10.10.10.1}    {255.255.255.0}

Environment Variables

wmic environment get name,username,variablevalue | findstr /i "path"

Output:

PATH|NT AUTHORITY\SYSTEM   C:\Windows\system32;C:\Windows;C:\Program Files\...
PATH|WORKGROUP\student     C:\Windows\system32;C:\Windows;C:\Users\student\...

Privesc relevance: Writable directories in PATH = PATH hijacking attack vector.


Using systeminfo with ExploitSuggester.py

What Is ExploitSuggester?

ExploitSuggester.py (by Alexander Hanel) correlates Windows OS version and installed patches against a database of known exploits to identify applicable privilege escalation vectors.

Workflow

# Step 1: On the target, save systeminfo output
systeminfo > systeminfo.txt

# Step 2: Transfer to your attack machine
# (via SMB, wget, etc.)

# Step 3: Run ExploitSuggester
python3 exploit-suggester.py --systeminfo systeminfo.txt --update
python3 exploit-suggester.py --systeminfo systeminfo.txt

Example Output

[*] Advisory: MS16-032
[*]   Title: Security Update for Windows
[*]   Impact: Elevation of Privilege
[*]   Exchange: https://www.exploit-db.com/exploits/40560
[*]   Impact: SYSTEM
[*]   Verified: Yes
[*]   Download URL: https://www.exploit-db.com/download/40560

[*] Advisory: MS17-010
[*]   Title: Security Update for Windows
[*]   Impact: Elevation of Privilege
[*]   Exchange: https://www.exploit-db.com/exploits/42066
[*]   Impact: SYSTEM
[*]   Verified: Yes

Key ExploitSuggester Output Fields

Field Meaning
Advisory Microsoft security bulletin number
Title Name of the update/vulnerability
Impact What the exploit achieves (usually “Elevation of Privilege”)
Exchange Link to Exploit-DB for the exploit code
Verified Whether the exploit has been confirmed working
Download URL Direct link to download the exploit

Exam Tip: Always check the “Verified” field. Unverified exploits may not work and waste exam time. Also check the exploit date — newer exploits are more likely to work on patched systems.


VM Detection and Why It Matters

Detection Methods

# Check system manufacturer
systeminfo | findstr /i "manufacturer"
# Output: System Manufacturer: VMware, Inc.

# Check BIOS
wmic bios get manufacturer
# Output: Phoenix Technologies LTD

# Check for VM-specific processes
tasklist | findstr /i "vmtoolsd vmware svchost"

# Check registry
reg query "HKLM\HARDWARE\DESCRIPTION\System\SystemBiosVersion"

# Check MAC address (VMware: 00:0C:29, VirtualBox: 08:00:27)
ipconfig /all | findstr /i "physical address"

Common VM Indicators

Indicator VMware VirtualBox Hyper-V
Manufacturer VMware, Inc. innotek GmbH Microsoft Corporation
Model VMware Virtual Platform VirtualBox Virtual Machine
MAC Prefix 00:0C:29, 00:50:56 08:00:27 Various
Processes vmtoolsd.exe, VMwareUser.exe VBoxService.exe None specific
BIOS Phoenix Technologies innotek GmbH American Megatrends
Registry HKLM\SOFTWARE\VMware, Inc. HKLM\SOFTWARE\Oracle\VirtualBox Guest Additions —

Why VM Detection Matters for Privesc

  1. VM Tools Vulnerabilities: VMware Tools, VirtualBox Guest Additions, and Hyper-V Integration Services have had privilege escalation vulnerabilities
  2. Shared Folders: VM shared folders may have weak permissions
  3. Copy/Paste Buffer: Some VM tools enable clipboard sharing — potential data exfiltration
  4. Known OSCP Boxes: Most OSCP labs use VMs. Knowing the platform helps identify common misconfigurations

Network Enumeration — Why It Matters for Privesc

Routes and Network Topology

The routing table reveals:

  • Multi-homed systems: Multiple NICs with routes to different subnets = pivot opportunities
  • Internal networks: Routes to 172.16.x.x or 10.x.x.x networks behind the target
  • Default gateway: The path out — may be a firewall or router with its own vulnerabilities

ARP Table

The ARP table shows:

  • Live hosts: Other machines on the same subnet
  • Gateway: The router’s MAC address
  • Broadcast addresses: Network configuration

Netstat Output

Active connections reveal:

  • Listening services: Attack surface (each service is a potential vulnerability)
  • Outbound connections: Where is this machine talking to? Domain controllers? Other servers?
  • ESTABLISHED sessions: Active lateral movement paths

Correlation Matrix: Information to Exploit Category

graph TD
    subgraph "Gathered Information"
        A[OS Version + Build]
        B[Missing Patches / KB Numbers]
        C[Architecture 32/64]
        D[Running Services]
        E[Installed Software]
        F[Network Config]
        G[User/Group Info]
        H[File Permissions]
    end
    
    subgraph "Exploit Categories"
        I[Kernel Exploits]
        J[Service Exploitation]
        K[Software-Specific Exploits]
        L[Token Manipulation]
        M[Credential Attacks]
        N[PATH/DLL Hijacking]
    end
    
    A --> I
    B --> I
    C --> I
    D --> J
    D --> N
    E --> K
    E --> N
    F --> L
    G --> M
    G --> L
    H --> N
    H --> J

Practical Correlation Table

Information Collected Maps To Example Attack
OS Build 17763, missing KB4562830 Kernel exploit PrintNightmare (CVE-2021-1675)
Service with unquoted path Service exploitation Unquoted service path → binary placement
Writable PATH directory PATH hijacking Place python.exe in writable PATH dir
SeImpersonatePrivilege Token manipulation JuicyPotato / RoguePotato
Outdated Java installation Software exploit Java applet exploit, JRE vulnerability
Admin in Backup Operators Credential attack SAM extraction via shadow copy
Open SMB share with write access File-based attack Upload and execute payload

Enumeration Flow Diagram

graph TD
    A[Initial Access] --> B[whoami /all]
    B --> C[systeminfo > systeminfo.txt]
    C --> D[ver]
    D --> E[wmic os get osarchitecture]
    E --> F[wmic qfe get HotFixID,InstalledOn]
    F --> G[hostname]
    G --> H[ipconfig /all]
    H --> I[arp -a]
    I --> J[route print]
    J --> K[netstat -ano]
    K --> L[net user]
    L --> M[net localgroup Administrators]
    M --> N[net accounts]
    N --> O[Check installed software]
    O --> P[Check running services]
    P --> Q[Check file permissions]
    Q --> R[Correlate findings]
    R --> S{Exploit Available?}
    S -->|Yes| T[Select best exploit]
    S -->|No| U[Continue deeper enumeration]
    U --> V[PowerUp / WinPEAS]
    V --> R
    
    style A fill:#ff9999
    style T fill:#99ff99
    style C fill:#ffff99

“What to Look For” Checklist

  • OS version and build number — Match to known exploits
  • Architecture (32/64-bit) — Select correct exploit binary
  • Missing patches — Cross-reference with ExploitSuggester
  • Installed software — Outdated versions with known CVEs
  • Running services — Non-standard services with potential misconfigurations
  • Network configuration — Multiple NICs, internal routes, pivot opportunities
  • Listening ports — Services that can be exploited remotely
  • Active connections — Lateral movement paths
  • Firewall state — Open/closed attack surface
  • VM detection — VM-specific vulnerabilities
  • Domain membership — AD vs workgroup changes attack surface dramatically

Common Mistakes

Mistake 1: Not Saving systeminfo Output

You need the systeminfo output for ExploitSuggester.py. If you don’t save it early, you’ll have to re-run it later (and the output may change if patches are installed).

Mistake 2: Ignoring the Architecture

Running a 32-bit exploit on a 64-bit system (or vice versa) will fail. Always confirm with wmic os get osarchitecture or echo %PROCESSOR_ARCHITECTURE%.

Mistake 3: Not Checking for Multiple Network Interfaces

A second NIC on an internal network is a pivot opportunity. ipconfig /all and route print reveal these.

Mistake 4: Skipping Hotfix Enumeration

The difference between an exploitable system and a patched one is often a single KB update. Always run wmic qfe get HotFixID.

Mistake 5: Not Correlating Findings

Collecting data is useless without analysis. After gathering all information, step back and ask: “What does this combination of OS version, missing patches, running services, and user privileges tell me about my best attack path?”


Quick Reference Command Cheat Sheet

# Essential system info
systeminfo > C:\temp\systeminfo.txt 2>&1
ver
hostname

# Architecture
wmic os get osarchitecture
echo %PROCESSOR_ARCHITECTURE%

# Patches
wmic qfe get Caption,Description,HotFixID,InstalledOn > C:\temp\hotfixes.txt 2>&1

# Network
ipconfig /all
arp -a
route print
netstat -ano

# Firewall
netsh advfirewall show allprofiles

# PowerShell alternatives
Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber, OSArchitecture
Get-HotFix | Select-Object HotFixID, Description, InstalledOn
Get-Process | Select-Object Name, Id, Path

# Installed software (fast)
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" | Select-Object DisplayName, DisplayVersion | Where-Object DisplayName

# VM detection
systeminfo | findstr /i "manufacturer model"
wmic bios get manufacturer