CPSA ยท Unix user enumeration and mail/file services
The finger service
What fingerd returns, where the data comes from and how it is abused.
Key points
- fingerd listens on TCP 79.
- A client sends a one-line query; an empty query lists online users, a name returns details about that user such as full name, login state and any user information file (for example .plan).
- That data comes from system account records and login records.
- Attackers use it to learn valid accounts and habits; the fix is to disable it.
Source: https://www.rfc-editor.org/rfc/rfc1288.html
Practice questions
Which TCP port does the finger service use?
- 23
- 79
- 111
- 513
Show answer
Answer: B. 79
RFC 1288 assigns finger to TCP port 79.
Which items can a finger query typically disclose?
- The user's full name
- Whether the user is logged in and idle time
- Contents of the user's .plan information file
- The user's password hash
- The host's firewall rule set
Show answer
Answer: A. The user's full name, B. Whether the user is logged in and idle time, C. Contents of the user's .plan information file
Finger returns the user's full name, login status and any user information file the administrator allows. It does not hold password hashes or firewall rules.
A finger request such as user@hostA@hostB is harmless, because it only returns public data.
Show answer
Answer: False
False. This is a forwarding query: hostB passes it on to hostA. RFC 1288 advises refusing forwarding by default because it can be used to reach hosts through a gateway or hide the real source.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
