CVE-2000-0377
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 · uneditedThe Remote Registry server in Windows NT 4.0 allows local authenticated users to cause a denial of service via a malformed request, which causes the winlogon process to fail, aka the "Remote Registry Access Authentication" vulnerability.
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 confidenceWindows NT 4.0 Remote Registry server contains a flaw where a local authenticated user sending a malformed request causes the winlogon process to fail, resulting in a denial of service. This is a local privilege escalation DoS rather than a remote vulnerability.
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= 4.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 the Windows versionRun 'winmsd' or check System Properties > General to confirm the exact Windows version. On NT 4.0, the OS displays as 'Windows NT Workstation 4.0' or 'Windows NT Server 4.0'.Affected if The OS is Windows NT 4.0 (any edition)
-
Check Remote Registry service statusOpen Services applet (services.msc) or run 'net start' command to list running services. Locate the 'Remote Registry' service in the list.Affected if The Remote Registry service is running or set to Automatic start
-
Verify service configurationRight-click the Remote Registry service in Services, select Properties, and note the Startup type and Service status fields.Affected if Startup type is set to Automatic or Started, making the service active
-
Review Event Viewer for winlogon crashesOpen Event Viewer (eventvwr.exe) and check System log for Event ID 1000 (Application Error) with 'winlogon.exe' as the faulting module, or Event ID 7034 indicating service crashes.Affected if Recent winlogon.exe crashes or service failures are logged after authenticated user activity
A system is affected if it runs Windows NT 4.0 with the Remote Registry service enabled, as the malformed request from a local authenticated user can crash winlogon.
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 dataDisable the Remote Registry service if not required; for Windows NT 4.0 systems, the only reliable remediation is decommissioning or isolating the affected systems given extended support ended years ago.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0377 — 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-0377 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