Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-0198: finger .@host on some systems may print information on some user accounts.

0
High
VulnerabilityCVE-1999-0198cve-1999-0198
Published: Fri Jan 01 1999 (01/01/1999, 05:00:00 UTC)
Source: NVD

Description

finger .@host on some systems may print information on some user accounts.

AI-Powered Analysis

AILast updated: 06/29/2025, 07:56:28 UTC

Technical Analysis

CVE-1999-0198 is a vulnerability related to the 'finger' protocol and command, which was historically used on Unix and Unix-like systems to retrieve information about user accounts on a remote host. Specifically, the vulnerability arises when executing the command 'finger .@host' on some systems, which may inadvertently disclose sensitive information about certain user accounts. This information leakage can include usernames, real names, login status, idle times, and potentially other details that could aid an attacker in reconnaissance activities. The vulnerability is notable for its high CVSS score of 10, indicating critical severity, with a vector indicating network attack vector (AV:N), low attack complexity (AC:L), no authentication required (Au:N), and full impact on confidentiality, integrity, and availability (C:C/I:C/A:C). Despite the high score, this vulnerability dates back to 1999 and affects legacy systems where the finger service is enabled and accessible. Modern systems typically disable or do not install the finger service by default, and many networks block the associated port (TCP 79). There is no patch available, likely because the finger service is deprecated or removed in most environments. The lack of known exploits in the wild suggests limited active exploitation, but the potential for information disclosure remains a concern in legacy or poorly secured systems.

Potential Impact

For European organizations, the impact of CVE-1999-0198 primarily involves the unauthorized disclosure of user account information, which can facilitate further targeted attacks such as social engineering, brute force login attempts, or privilege escalation. While the finger service itself does not directly allow system compromise, the leakage of user details undermines confidentiality and can be a stepping stone for attackers. Organizations relying on legacy Unix systems or those with finger service enabled and exposed to external or internal networks are at risk. This can be particularly impactful for sectors with stringent data protection requirements, such as finance, healthcare, and government, where user information leakage could violate GDPR and other privacy regulations. Additionally, the vulnerability's ease of exploitation without authentication means attackers can gather information stealthily, increasing the risk of subsequent attacks.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Audit their network and systems to identify any active finger services, especially on legacy Unix or Unix-like hosts. 2) Disable the finger service entirely if it is not required, as it is largely obsolete and unnecessary in modern environments. 3) If finger service must remain enabled, restrict access using firewall rules to limit exposure only to trusted internal networks and block external access on TCP port 79. 4) Employ network intrusion detection systems (NIDS) to monitor for unusual finger protocol traffic. 5) Conduct regular security assessments and penetration tests to ensure no unintended information disclosure occurs. 6) Educate system administrators about the risks associated with legacy services and encourage migration to more secure alternatives. 7) Implement strict user account management and monitoring to detect suspicious activities that may follow reconnaissance attempts.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32bb6fd31d6ed7deba8

Added to database: 5/20/2025, 3:43:39 PM

Last enriched: 6/29/2025, 7:56:28 AM

Last updated: 2/7/2026, 12:05:51 PM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats