CVE-2000-0793
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 · uneditedNorton AntiVirus 5.00.01C with the Novell Netware client does not properly restart the auto-protection service after the first user has logged off of the system.
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 confidenceNorton AntiVirus 5.00.01C when deployed with the Novell Netware client fails to properly restart its auto-protection service after the first user logs off the system. This leaves the system vulnerable as the real-time scanning protection becomes inactive following user logoff.
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.1= 5.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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Norton AntiVirus versionCheck the installed version of Norton AntiVirus on the system. This can typically be found in Add/Remove Programs, the program's About section, or by checking the executable version information (e.g., right-click nav.exe or the program files directory).Affected if The installed version is Norton AntiVirus 5.00.01C specifically.
-
Identify Novell Client versionCheck the installed version of the Novell NetWare client software. This can be found in Add/Remove Programs under Novell client entries, or by checking the client software's version information in the system or network configuration.Affected if The installed Novell Client version is 3.1.
-
Confirm both products coexistVerify that both Norton AntiVirus 5.00.01C and Novell Client 3.1 are installed on the same system. The vulnerability only manifests when both are present together.Affected if Both products are installed concurrently on the same machine.
-
Test auto-protection service after logoffLog in with one user, verify Norton AntiVirus auto-protection is active, then log off that user and log in with a different user. Check whether the auto-protection service (NAV Auto-Protect or similar) is running. This can be done via Task Manager, Services console, or the Norton AntiVirus interface.Affected if The auto-protection service is NOT running or inactive after the first user logs off, leaving real-time scanning disabled.
A system is affected if it has Norton AntiVirus 5.00.01C installed alongside Novell Client 3.1, and the auto-protection service fails to restart after a user logs off, resulting in inactive real-time scanning protection.
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 from the obsolete Norton AntiVirus 5.00.01C to a current supported version, or ensure the auto-protection service is configured to restart properly after user logoff events.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0793 — 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-0793 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