CVE-2002-0929
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 · uneditedBuffer overflows in the DHCP server for NetWare 6.0 SP1 allow remote attackers to cause a denial of service (reboot) via long DHCP requests.
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 confidenceBuffer overflow vulnerability in the DHCP server component of NetWare 6.0 SP1 allows remote attackers to send specially crafted DHCP requests with excessive length, triggering a buffer overflow that causes the server to reboot (denial of service).
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= 6.0CVSS 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 NetWare versionRun 'VERSION' command at the server console or check the welcome screen on boot. Alternatively, query the Novell NLM version or check in the 'Monitor' utility under 'System Information'.Affected if Version is not NetWare 6.0 (e.g., 5.x or newer than 6.0)
-
Confirm Service Pack levelAt the server console, type 'SPSTATUS' or check the 'About' section in the NetWare Administrator (NWADMN32) or the Monitor utility. Look for SP1 specifically.Affected if System shows SP1 is installed (the vulnerability is present in NetWare 6.0 with SP1)
-
Verify DHCP server is runningAt the server console, type 'DHCP' or use the 'Monitor' utility, select 'NLM Information' and search for 'DHCPSRVR.NLM' or 'DHCP' to see if the DHCP server component is loaded and running.Affected if DHCP server NLM is loaded and active on the system
-
Check network exposure of DHCP serviceReview the server network configuration and firewall rules. DHCP uses UDP ports 67/68. Determine if these ports are accessible from untrusted networks or the internet.Affected if The DHCP server is reachable from network segments that could contain malicious attackers
If the system is NetWare 6.0 with SP1 installed and the DHCP server component is actively running and network-accessible, it is affected by this vulnerability.
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 dataApply the appropriate Novell patch for NetWare 6.0 SP1 to address the DHCP server buffer overflow, or consider upgrading to a supported NetWare version if patches are no longer available for this legacy system.
- 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-2002-0929 — 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-2002-0929 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