PT0-003 Exam Dumps : CompTIA PenTest+ Exam

Capturing plaintext credentials in network traffic is done using packet sniffing. Wireshark is the best tool for this task.

Option A (Burp Suite) ❌: Used for web application testing and intercepting HTTPS traffic, but not general network sniffing.

Option B (Wireshark) ✅: Correct.

Wireshark is a packet analysis tool that captures unencrypted network traffic, including plaintext credentials.

Option C (ZAP - Zed Attack Proxy) ❌: Similar to Burp Suite, but focused on web application security, not network packet capture.

Option D (Metasploit) ❌: Metasploit is used for exploitation rather than capturing traffic.

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – Packet Sniffing & Network Traffic Analysis

Based on the Nmap scan results, the services identified on the target server are as follows:

22/tcp open ssh:

Service: SSH (Secure Shell)

Function: Provides encrypted remote access.

Attack Surface: Brute force attacks or exploiting vulnerabilities in outdated SSH implementations. However, it is generally considered secure if properly configured.

25/tcp filtered smtp:

Service: SMTP (Simple Mail Transfer Protocol)

Function: Email transmission.

Attack Surface: Potential for email-related attacks such as spoofing, but the port is filtered, indicating that access may be restricted or protected by a firewall.

111/tcp open rpcbind:

Service: RPCBind (Remote Procedure Call Bind)

Function: Helps in mapping RPC program numbers to network addresses.

Attack Surface: Can be exploited in specific configurations, but generally not a primary target compared to others.

2049/tcp open nfs:

Service: NFS (Network File System)

Function: Allows for file sharing over a network.

Attack Surface: NFS can be a significant target for attacks due to potential misconfigurations that can allow unauthorized access to file shares or exploitation of vulnerabilities in NFS services.

Conclusion: The NFS service (2049/tcp) provides the best target for launching an attack. File sharing services like NFS often contain sensitive data and can be vulnerable to misconfigurations that allow unauthorized access or privilege escalation.

When a penetration tester discovers hard-coded credentials in a file within an unprotected source code repository, the next steps should focus on documentation and further investigation to identify additional security issues.

Taking a Screen Capture (Option B):

Documentation: It is essential to document the finding for the final report. A screen capture provides concrete evidence of the discovered hard-coded credentials.

Audit Trail: This ensures that there is a record of the vulnerability and can be used to communicate the issue to stakeholders, such as the development team or the client.

Investigating for Other Embedded Passwords (Option C):

Thorough Search: Finding one hard-coded password suggests there might be others. A thorough investigation can reveal additional credentials, which could further compromise the security of the system.

Automation Tools: Tools like truffleHog, git-secrets, and grep can be used to scan the repository for other instances of hard-coded secrets.

Pentest References:

Initial Discovery: Discovering hard-coded credentials often occurs during source code review or automated scanning of repositories.

Documentation: Keeping detailed records of all findings is a critical part of the penetration testing process. This ensures that all discovered vulnerabilities are reported accurately and comprehensively.

Further Investigation: After finding a hard-coded credential, it is best practice to look for other security issues within the same repository. This might include other credentials, API keys, or sensitive information.

Steps to Perform:

Take a Screen Capture:

Use a screenshot tool to capture the evidence of the hard-coded credentials. Ensure the capture includes the context, such as the file path and relevant code lines.

Investigate Further:

Use tools and manual inspection to search for other embedded passwords.

Commands such as grep can be helpful:

grep -r ' password ' /path/to/repository

Tools like truffleHog can search for high entropy strings indicative of secrets:

trufflehog --regex --entropy=True /path/to/repository

By documenting the finding and investigating further, the penetration tester ensures a comprehensive assessment of the repository, identifying and mitigating potential security risks effectively.

======