Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA Exam PT0-003 Topic 3 Question 27 Discussion

Actual exam question for CompTIA's PT0-003 exam
Question #: 27
Topic #: 3
[All PT0-003 Questions]

[Information Gathering and Vulnerability Scanning]

A penetration tester observes the following output from an Nmap command while attempting to troubleshoot connectivity to a Linux server:

Starting Nmap 7.91 ( https://nmap.org ) at 2024-01-10 12:00 UTC

Nmap scan report for example.com (192.168.1.10)

Host is up (0.001s latency).

Not shown: 9999 closed ports

PORT STATE SERVICE

21/tcp open ftp

80/tcp open http

135/tcp open msrpc

139/tcp open netbios-ssn

443/tcp open https

2222/tcp open ssh

444/tcp open microsoft-ds

Nmap done: 1 IP address (1 host up) scanned in 0.23 seconds

Which of the following is the most likely reason for the connectivity issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

The key detail in the Nmap scan output is that port 2222/tcp is open and running the SSH service. The standard SSH port is 22, so if the tester was attempting to connect on port 22, they would not succeed because SSH is instead listening on port 2222.

This is a common security hardening tactic---moving services to non-standard ports to reduce automated attacks.

There is no indication that the service is blocked (B), or requires certificates (C), or is inactive (D), because Nmap clearly shows the service is open and identified.

CompTIA PenTest+ Reference:

PT0-003 Objective 3.3: Analyze tool output or data related to engagement activities.

Nmap usage and interpreting scan results is emphasized in multiple sections.


Contribute your Thoughts:

Jade
3 days ago
Ha, D all the way! The SSH service is not active. Typical Linux admin, forgetting to start the service. Classic!
upvoted 0 times
...
Bobbye
6 days ago
Hmm, C seems more likely. The SSH service requires certificate authentication. Gotta love those extra security layers.
upvoted 0 times
...
Tracey
6 days ago
I agree with Emerson, that could be the reason for the connectivity issue.
upvoted 0 times
...
Emerson
7 days ago
I think the SSH service is running on a different port.
upvoted 0 times
...
Lelia
11 days ago
I'm going with B. The SSH service is blocked by a firewall. Looks like they have some tight security measures in place.
upvoted 0 times
...
Melissa
15 days ago
The SSH service is running on a different port, that's gotta be the issue. 2222, really? Whoever set up this server has some weird preferences.
upvoted 0 times
Devora
5 days ago
A) The SSH service is running on a different port.
upvoted 0 times
...
Dorothy
13 days ago
A: Yeah, it's strange to have SSH running on port 2222. That could definitely be causing the connectivity issue.
upvoted 0 times
...
...

Save Cancel