← Back to Feed CACHED · 2026-10-07 05:17:11 · CACHE_KEY CVE-1999-0001
CVE-1999-0001 · CWE-20 · Disclosed 1999-12-30

BSD ip_input.c IP Fragment Reassembly Denial of Service

ASSESSED — NOISGATE
Vendor
—
—
—
Reassessed
—
—
—
Verdict: —
Do you agree?
01 · The Real Story

Like posting a recall for horse-drawn carriages in a world that drives electric cars

CVE-1999-0001 — literally the first CVE identifier ever assigned — is a denial-of-service flaw in ip_input.c, the IPv4 packet reassembly path shared across BSD-derived TCP/IP stacks. A remote, unauthenticated attacker could send crafted IP fragments that crash or hang the kernel network stack. The affected versions are FreeBSD 1.0 through 3.0, OpenBSD 2.3–2.4, and BSDI BSD/OS 3.1. Every one of these reached end-of-life between May 1999 and December 1999. BSDI, the company, no longer exists. No fix was ever backported because the vendors moved on to entirely new major releases within months of disclosure.

The vendor CVSS v2 score of 5.0 (MEDIUM) was a reasonable rating *in 1999* — remote, no-auth, low-complexity, partial-availability impact. But in October 2026, the rating is academically generous. There is no realistic installed base for these OS versions anywhere on Earth. Modern FreeBSD (14.x) and OpenBSD (7.x) rewrote and hardened their IP stacks decades ago. The flaw has zero relevance to any system a defender could plausibly be managing. The vendor severity doesn't match reality — it *wildly overstates* it — because the software is extinct.

"A 27-year-old DoS in operating systems that no longer exist. File it and move on."
02 · The Attack Path

3 steps from start to impact.

STEP 01

Locate a surviving host

The attacker must first identify a system running FreeBSD ≤3.0, OpenBSD 2.3–2.4, or BSDI 3.1 that is network-reachable. These operating systems have been end-of-life for over 25 years. No major scanner fingerprint database (Shodan, Censys, GreyNoise) returns meaningful populations of these versions on the public internet. A host in this state would be an extraordinary anomaly, likely an unpowered museum exhibit.
Conditions required:
  • Target must be running FreeBSD ≤3.0, OpenBSD 2.3–2.4, or BSDI BSD/OS 3.1
  • Target must be network-reachable on an IP-routable interface
Where this breaks in practice:
  • All affected versions reached EOL between 1999 and 2000
  • BSDI the company no longer exists
  • No hardware driver support for modern NICs or motherboards makes running these OSes nearly impossible on post-2005 hardware
  • Virtualization of these ancient kernels is fragile and non-standard
STEP 02

Craft malicious IP fragments

The attacker crafts IP packets that exploit the improper input validation in ip_input.c. The exact triggering condition involves malformed fragment reassembly metadata that the kernel fails to validate before processing. No weaponized tooling circulates for this vulnerability — the 17 GitHub repos referencing the CVE are metadata indexes and educational collections, not functional exploit code.
Conditions required:
  • Ability to send raw IP packets to the target
  • Knowledge of the specific fragment malformation trigger
Where this breaks in practice:
  • No public functional exploit code exists
  • Modern ISP and enterprise firewalls drop malformed IP fragments by default
  • Any IDS/IPS deployed since ~2002 would flag anomalous IP fragment patterns
STEP 03

Trigger kernel DoS

If the crafted fragments reach the target kernel, the ip_input.c code path crashes or hangs the TCP/IP stack, causing a denial of service. The impact is availability only — no code execution, no data exfiltration, no privilege escalation. Recovery requires a reboot. There is no persistence mechanism.
Conditions required:
  • Malformed packets must traverse all network-layer defenses to reach the kernel
Where this breaks in practice:
  • Impact is temporary DoS, not RCE
  • A reboot restores service
  • No confidentiality or integrity impact
Detection/coverage: No modern vulnerability scanner checks for this CVE. Nessus, Qualys, and Rapid7 do not carry plugins for FreeBSD ≤3.0 or OpenBSD 2.x.
03 · Compensating Control

1
IGNORE 0.0→IGNORE 0.0
Confirm you do not run affected versions — Run a software inventory query across your CMDB or asset management platform (e.g., ServiceNow, Qualys, Rapid7) filtering for FreeBSD ≤3.0, OpenBSD 2.3–2.4, or BSDI BSD/OS 3.1. You will find zero results. This is a documentation exercise only. No mitigation SLA applies — the noisgate verdict is IGNORE.
What doesn't work
  • Patching the affected OS — no patches exist and the vendor (BSDI) is defunct; FreeBSD and OpenBSD never backported fixes because they shipped new major versions instead.
  • Deploying a WAF or IPS signature — no vendor maintains a signature for this CVE; writing one is wasted effort for a zero-population threat.
  • Upgrading to a fixed version of the same branch — there is no fixed version within the affected branches; the 'fix' was moving to an entirely different OS release over 25 years ago.
04 · Intelligence Metadata

The supporting signals.

In-the-wild exploitationNone. Not listed on CISA KEV. No campaigns, no threat-actor TTPs, no incident reports reference this CVE in any timeframe.
Proof-of-concept availabilityNo functional PoC exists. 17 GitHub repos reference the CVE ID but are metadata aggregators (e.g., d2cy/CVEs, pwnfuzz/cve-pocs) — none contain working exploit code. ExploitDB has no entry. pocindex.io returns no specific PoC. Nuclei has no template.
EPSS score0.03351 (88th percentile). Misleadingly high — EPSS models weight network-reachable/no-auth/low-complexity vectors. The model cannot account for a zero-percent installed base of the affected software.
KEV statusNot listed. Never added to CISA KEV. No due date. No binding operational directive applies.
CVSS vectorAV:N/AC:L/Au:N/C:N/I:N/A:P (v2 Base 5.0, MEDIUM). NVD also assigned a v3.x score of 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Both scores describe the *theoretical* exploitability of the code bug in isolation — neither considers the extinction of the host population.
Affected versionsFreeBSD 1.0, 1.1, 1.1.5.1, 1.2, 2.0, 2.0.5, 2.1.0, 2.1.5, 2.1.6, 2.1.7, 2.2, 2.2.2, 2.2.5, 2.2.6, 2.2.8, 3.0 · OpenBSD 2.3, 2.4 · BSDI BSD/OS 3.1
Fixed versionsNone formally issued. The bug was superseded by wholesale OS version upgrades (FreeBSD 3.1+, OpenBSD 2.5+). No backport patches were released for EOL branches.
Scanning / exposure dataZero measurable attack surface. Shodan, Censys, and GreyNoise return no meaningful population of FreeBSD ≤3.0 or OpenBSD 2.x hosts. BSDI hosts are non-existent.
Disclosure & creditDisclosed 1999-12-30. One of the original batch of CVE IDs issued by MITRE. The specific discovering researcher is not attributed in public records. Steve Christey Coley (MITRE) has noted on X that CVE-1999-0001 exemplifies early CVE ambiguity — it may conflate multiple related bugs in shared BSD networking code.
Distro / downstream impactNo modern Linux or BSD distribution carries the vulnerable code. The ip_input.c reassembly path was rewritten in FreeBSD 4.x (2000) and OpenBSD 2.5+ (1999). macOS, iOS, and other Apple platforms diverged from this codebase long before the flaw was relevant.

Sources.

  1. NVD — CVE-1999-0001 Detail
  2. CVE CIRCL — CVE-1999-0001
  3. Snyk — Improper Input Validation in FreeBSD
  4. CVEFeed — CVE-1999-0001
  5. Tenable — CVE-1999-0001
  6. Steve Christey Coley on CVE-1999-0001 ambiguity (X)
  7. endoflife.date — FreeBSD lifecycle
  8. endoflife.date — OpenBSD lifecycle
05 · The Call

Final Verdict
↓ DOWNGRADED to IGNORE (0.0/10)

Why this verdict

  • Extinct installed base: Every affected OS version (FreeBSD ≤3.0, OpenBSD 2.3–2.4, BSDI 3.1) reached end-of-life between May 1999 and December 1999. BSDI as a company is defunct. The probability of encountering a live, network-reachable instance of any affected version in a 2026 enterprise is effectively zero.
  • DoS-only impact with no escalation path: Even if a host existed, the worst outcome is a temporary kernel hang requiring a reboot. There is no code execution, no data exposure, no lateral movement. This caps the *theoretical* ceiling well below CRITICAL even in 1999.
  • No exploitation ecosystem: No functional PoC, no weaponized tool, no KEV listing, no threat-actor interest, no scanner coverage. The vulnerability has never been exploited in a documented incident in 27 years.
  • Role multiplier: In the late 1990s, these BSDs served as firewalls, routers, and servers — roles where a DoS could matter. In 2026, 0% of those roles are served by these versions. Modern FreeBSD 14.x and OpenBSD 7.x do not contain the vulnerable code. No high-value-role analysis is applicable because the installed base is 0%, far below the 1% floor required to invoke the verdict floor rule.

Why not higher?

There is no scenario in which this CVE warrants any severity rating in 2026. The affected software is extinct. The impact is DoS-only. There is no PoC, no exploitation history, no scanner coverage, and no enterprise on Earth is running patching cycles against FreeBSD 3.0. Assigning even LOW would overstate the risk.

Why not lower?

IGNORE is the lowest possible verdict. There is nothing below it.

06 · Verification

Crowdsourced verification payload.

Run on any Linux or BSD auditor workstation as an unprivileged user. Pass the target hostname or IP as the first argument: ./check_cve_1999_0001.sh 10.0.0.5. No special privileges are needed — the script connects via SSH to read the remote OS version string. Requires ssh and uname availability on the target.

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# check_cve_1999_0001.sh — CVE-1999-0001 applicability check
# Checks whether a remote host runs an affected BSD version.
# Usage: ./check_cve_1999_0001.sh <host>
# Exit codes: 0 = PATCHED/NOT_AFFECTED, 1 = VULNERABLE, 2 = UNKNOWN

set -euo pipefail

if [[ $# -lt 1 ]]; then
  echo "Usage: $0 <hostname_or_ip>"
  exit 2
fi

HOST="$1"

# Try to get OS info via uname
OS_INFO=$(ssh -o ConnectTimeout=5 -o BatchMode=yes "$HOST" 'uname -sr' 2>/dev/null) || {
  echo "UNKNOWN — could not connect to $HOST via SSH."
  exit 2
}

case "$OS_INFO" in
  FreeBSD\ 1.*|FreeBSD\ 2.*|FreeBSD\ 3.0*)
    echo "VULNERABLE — $HOST runs $OS_INFO (affected by CVE-1999-0001)."
    exit 1
    ;;
  OpenBSD\ 2.3*|OpenBSD\ 2.4*)
    echo "VULNERABLE — $HOST runs $OS_INFO (affected by CVE-1999-0001)."
    exit 1
    ;;
  *BSD/OS\ 3.1*|*BSDI\ 3.1*)
    echo "VULNERABLE — $HOST runs $OS_INFO (affected by CVE-1999-0001)."
    exit 1
    ;;
  *)
    echo "PATCHED — $HOST runs $OS_INFO (not affected by CVE-1999-0001)."
    exit 0
    ;;
esac