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-0986: The ping command in Linux 2.0.3x allows local users to cause a denial of service by sending large pa

0
Medium
VulnerabilityCVE-1999-0986cve-1999-0986denial of service
Published: Wed Dec 08 1999 (12/08/1999, 05:00:00 UTC)
Source: NVD
Vendor/Project: debian
Product: debian_linux

Description

The ping command in Linux 2.0.3x allows local users to cause a denial of service by sending large packets with the -R (record route) option.

AI-Powered Analysis

AILast updated: 07/01/2025, 12:56:43 UTC

Technical Analysis

CVE-1999-0986 is a vulnerability affecting the ping command in Linux kernel versions 2.0.3x and related Debian Linux versions including 2.0 through 2.1 and some 5.x versions. The issue arises when local users invoke the ping utility with the -R (record route) option and send large packets. This misuse causes a denial of service (DoS) condition by overwhelming the system's ability to handle these oversized packets, potentially leading to a crash or system instability. The vulnerability is local, meaning the attacker must have access to the system to execute the ping command with crafted parameters. The CVSS score of 5.0 (medium severity) reflects that the impact is limited to availability, with no confidentiality or integrity compromise. No authentication is required beyond local user access, and no remote exploitation is possible. No patches are available, likely due to the age of the affected kernel versions, which are now obsolete and unsupported. The vulnerability is primarily a resource exhaustion or crash issue triggered by malformed ping packets using the record route option, which is rarely used in modern systems. This vulnerability is historical and affects legacy Linux systems that are no longer in widespread use or supported.

Potential Impact

For European organizations, the direct impact of this vulnerability today is minimal because it affects very old Linux kernel versions (2.0.x and early 2.1 and some 5.x versions) that are no longer deployed in production environments. Modern Linux distributions have long since replaced these kernels with more secure and stable versions. However, if any legacy systems running these old kernels remain in use within critical infrastructure, industrial control systems, or embedded devices, they could be susceptible to local DoS attacks by insiders or attackers with local access. Such a DoS could disrupt availability of critical services or systems, potentially impacting business continuity. The vulnerability does not allow remote exploitation, so the risk is limited to environments where local user access is possible. Given the age and nature of the vulnerability, it is unlikely to be exploited in the wild or pose a significant threat to contemporary European IT environments. Nonetheless, organizations with legacy Linux systems should be aware of this issue as part of their risk assessments.

Mitigation Recommendations

The primary mitigation is to upgrade or replace any systems running the affected Linux kernel versions with supported, modern Linux distributions that have patched or inherently do not contain this vulnerability. Since no patch is available for these old kernels, system upgrade is the only effective remediation. Additionally, organizations should restrict local user access to trusted personnel only, implement strict access controls, and monitor for unusual usage of the ping command or attempts to use the -R option with large packets. For legacy embedded or industrial systems that cannot be upgraded, network segmentation and isolation can reduce the risk of local exploitation. Employing host-based intrusion detection systems (HIDS) to alert on suspicious local commands may also help detect attempts to exploit this vulnerability. Finally, organizations should conduct audits to identify any legacy Linux systems still in operation and plan their decommissioning or upgrade.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32cb6fd31d6ed7df4d2

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

Last enriched: 7/1/2025, 12:56:43 PM

Last updated: 2/7/2026, 9:21:38 AM

Views: 38

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