CVE-2000-0310
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 · uneditedIP fragment assembly in OpenBSD 2.4 allows a remote attacker to cause a denial of service by sending a large number of fragmented packets.
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 · high confidenceOpenBSD 2.4 contains a vulnerability in its IP fragment assembly code where a remote attacker can cause a denial of service by sending a large number of fragmented IP packets, likely exhausting memory or processing resources during reassembly.
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= 2.4CVSS 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.
-
Verify OpenBSD versionRun `uname -a` or check the contents of `/etc/motd` to identify the installed OpenBSD version numberAffected if The version displayed is exactly 2.4
-
Confirm IP networking is enabledCheck if the system has IP networking active by running `ifconfig -a` to list network interfacesAffected if Any network interface shows an IP address, indicating the system is processing IP traffic including fragments
-
Check kernel fragment handlingInspect running network statistics with `netstat -s -p ip` to see if IP fragment reassembly is occurringAffected if Fragment-related counters are present and incrementing, confirming the vulnerable reassembly code path is in use
-
Look for exploitation symptomsRun `vmstat 1` and `ps aux` to check for unusually high memory usage or CPU consumption that could indicate fragment-based resource exhaustionAffected if System shows abnormally high memory or CPU usage with no obvious legitimate cause, potentially indicating the DoS condition
You are affected only if your system is running OpenBSD version 2.4 with IP networking enabled, as this specific version contains the vulnerable IP fragment assembly code.
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 dataSince OpenBSD 2.4 is extremely outdated (released 1998), the primary remediation is to upgrade to a supported OpenBSD version. Alternatively, implement edge filtering to block or rate-limit fragmented packets at network perimeter devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0310 — 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-0310 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