CompTIA PT0-003 Actual Questions

To reenter the system remotely after the patch for the recently exploited RCE vulnerability has been deployed, the penetration tester can use schtasks.exe and sc.exe.

schtasks.exe:

Purpose: Used to create, delete, and manage scheduled tasks on Windows systems.

Persistence: By creating a scheduled task, the tester can ensure a script or program runs at a specified time, providing a persistent backdoor.

Example:

schtasks /create /tn " Backdoor " /tr " C:\path\to\backdoor.exe " /sc daily /ru SYSTEM

sc.exe:

Purpose: Service Control Manager command-line tool used to manage Windows services.

Persistence: By creating or modifying a service to run a malicious executable, the tester can maintain persistent access.

Example:

sc create backdoor binPath= " C:\path\to\backdoor.exe " start= auto

Other Utilities:

rundll.exe: Used to run DLLs as applications, not typically used for persistence.

cmd.exe: General command prompt, not specifically used for creating persistence mechanisms.

chgusr.exe: Used to change install mode for Remote Desktop Session Host, not relevant for persistence.

netsh.exe: Used for network configuration, not typically used for persistence.

Pentest References:

Post-Exploitation: Establishing persistence is crucial to maintaining access after initial exploitation.

Windows Tools: Understanding how to leverage built-in Windows tools like schtasks.exe and sc.exe to create backdoors that persist through reboots and patches.

By using schtasks.exe and sc.exe, the penetration tester can set up persistent mechanisms that will allow reentry into the system even after the patch is applied.

======

XSS Attack Explanation:

The payload exploits Cross-Site Scripting (XSS) by injecting obfuscated JavaScript into the application. When rendered, the browser executes the malicious code (e.g., alert( ' pwned ' )).

Obfuscation ( < sCRitP > instead of < script > ) attempts to bypass naive input filters.

Countermeasure:

Implement input sanitization to ensure all user inputs are properly validated and escaped before being processed or rendered.

Other measures include using Content Security Policies (CSP) and output encoding.

Why Not Other Options?

A: This is not arbitrary code execution; it is a browser-based attack.

B: XSS is unrelated to SQL injection.

C: Cross-Site Request Forgery (CSRF) is a different vulnerability targeting session handling, not script injection.

CompTIA Pentest+ References:

Domain 3.0 (Attacks and Exploits)

OWASP XSS Prevention Cheat Sheet

The correct answer is D. Hydra

Hydra is a password-attack tool commonly used to test authentication services such as SSH, FTP, Telnet, RDP, HTTP, SMB, and others. In this scenario, the tester has a leaked password list and wants to verify whether any of those passwords can authenticate to an SSH server as a valid user. Hydra is the most appropriate tool because it can automate login attempts against SSH using usernames and password lists.

A is incorrect because BloodHound is used to analyze Active Directory relationships and identify attack paths. It is not used to test SSH logins with password lists.

B is incorrect because Responder is used to capture or poison network authentication traffic, commonly NTLM-related traffic. It is not the best tool for testing leaked passwords against SSH.

C is incorrect because Burp Suite is primarily used for web application testing. While it can test web logins, it is not designed for SSH authentication testing.

In PenTest+ terms, this falls under Attacks and Exploits, specifically password attacks, credential validation, and authentication testing against remote services.

In a cloud environment, testing for Server-Side Request Forgery (SSRF) vulnerabilities involves attempting to access metadata services. Here’s why the specified command is appropriate:

Accessing Cloud Metadata Service:

URL: is a well-known endpoint in cloud environments (e.g., AWS) to access instance metadata.

Purpose: By exploiting SSRF to access this URL, an attacker can retrieve sensitive information such as instance credentials and other metadata.

Comparison with Other Commands:

127.0.0.1/etc/passwd: This is more about local file inclusion, not specific to cloud metadata.

< script > alert(1) < /script > : This tests for XSS, not SSRF.

127.0.0.1: This is a generic loopback address and does not specifically test for metadata access in a cloud environment.

Using curl < url > is the correct approach to test for SSRF vulnerabilities in cloud environments to potentially expose secrets.

======