CVE-2000-0440
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNetBSD 1.4.2 and earlier allows remote attackers to cause a denial of service by sending a packet with an unaligned IP timestamp option.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNetBSD 1.4.2 and earlier contains a kernel-level vulnerability in IP packet handling where processing an unaligned IP timestamp option triggers a denial of service condition. The vulnerability is remotely exploitable via specially crafted packets.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.4= 4.0= 5.0= 1.4.1= 1.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed operating system versionRun 'uname -a' to display system information, or check /etc/motd or /var/run/dmesg.boot for version detailsAffected if The displayed version is FreeBSD 3.4, 4.0, or 5.0, or NetBSD 1.4.1 or 1.4.2
-
Confirm the system is a BSD derivativeCheck the kernel name from uname output or examine /etc/os-release if availableAffected if The operating system is identified as FreeBSD or NetBSD and matches the version criteria from step 1
-
Verify IP networking is enabledCheck if the network interface is configured by running 'ifconfig -a' to list network interfaces and their statusAffected if The system has active network interfaces configured with IP addresses, indicating the IP stack is in use
-
Confirm kernel is processing IP trafficUse 'netstat -i' or 'netstat -s' to display network statistics and verify IP protocol activityAffected if IP protocol statistics are present, showing the kernel is actively processing IP packets
A system is affected if it runs FreeBSD 3.4, 4.0, or 5.0 or NetBSD 1.4.1 or 1.4.2 with an active IP network stack, since the vulnerability lies in kernel-level IP timestamp option handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade NetBSD to version 1.4.3 or later, or apply the vendor patch that corrects IP timestamp option alignment handling in the kernel network stack.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0440 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data