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

The SecOps Group CNSP Exam - Topic 1 Question 12 Discussion

Posted by Vannessa on Jul 31, 2025 at 07:35 PM

If you find the 111/TCP port open on a Unix system, what is the next logical step to take?

Suggested Answer: A

Port 111/TCP is the default port for the RPC (Remote Procedure Call) portmapper service on Unix systems, which registers and manages RPC services.

Why A is correct: Running rpcinfo -p <hostname> queries the portmapper to list all registered RPC services, their programs, versions, and associated ports. This is a logical next step during a security audit or penetration test to identify potential vulnerabilities (e.g., NFS or NIS services). CNSP recommends this command for RPC enumeration.

Why other options are incorrect:

B . Telnet to the port to look for a banner: Telnet might connect, but RPC services don't typically provide a human-readable banner, making this less effective than rpcinfo.

C . Telnet to the port, send 'GET / HTTP/1.0' and gather information from the response: Port 111 is not an HTTP service, so an HTTP request is irrelevant and will likely fail.

D . None of the above: Incorrect, as A is a valid and recommended step.


Get Premium CNSP Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
18 comments · newest first
SH
Sherron 10 months ago
None of the above? Nah, I’d stick with A or B for sure.
DE
Desiree 10 months ago
I think B is better, banners can give a lot of info.
RA
Rasheeda 10 months ago
Wait, is 111/TCP even supposed to be open? That seems odd.
BE
Bernardo 10 months ago
C sounds interesting, but is it really the best option?
MO
Mona 11 months ago
Definitely go with A, rpcinfo is super useful!
YU
Yuonne 11 months ago
Honestly, I'm leaning towards option A, but I also remember something about checking for banners. It's tough to decide without more context!
RI
Rikki 11 months ago
I practiced a question like this where we had to gather information from a web server response. Sending 'GET / HTTP/1.0' might be relevant, but I can't recall if it's the right context for port 111.
HI
Hildegarde 11 months ago
I feel like telnetting to the port could give us some useful info, especially if there's a banner. That seems like a safe bet.
KR
Kris 11 months ago
I think I remember that running 'rpcinfo -p' is a common step when dealing with RPC services, but I'm not entirely sure if it's the best first move here.
HU
Hubert 12 months ago
Hmm, I'm not sure about this one. I'll have to think it through a bit more. Maybe I'll just mark 'None of the above' for now and come back to it later.
MA
Marquetta 12 months ago
Interesting, I haven't seen that port number before. I think I'd try option C and send a GET request to see if I can gather any useful information from the response.
SH
Shanda 12 months ago
Okay, this one seems straightforward. I'd go with option B and just telnet to the port to check the banner and see what's running on that port.
AM
Amalia 1 year ago
Hmm, the 111/TCP port is often associated with RPC services, so I'd probably go with option A and run 'rpcinfo -p' to see what's running.
ME
Mertie 1 year ago
Nah, I'm going with C. Gotta get that juicy banner information, you know? Who needs RPC when you can just brute-force your way in?
EL
Elli 1 year ago
↳ replying to Mertie
User 1: I think I'll go with A, enumerating RPC services seems like a good idea.
TH
Thersa 1 year ago
Hmm, telnet to the port and send a GET request? That's so old-school, I'm going with option A - gotta love those RPC services!
ER
Erick 1 year ago
↳ replying to Thersa
User1: I agree, option A seems like the way to go.
EL
Elroy 1 year ago
I think the next logical step is to run 'rpcinfo -p ' to enumerate the RPC services.
0/2000 characters

Save Cancel