CVE-1999-0504
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 · uneditedA Windows NT local user or administrator account has a default, null, blank, or missing password.
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 local user or administrator accounts are configured with default, null, blank, or missing passwords, allowing unauthenticated remote or local attackers to gain unauthorized access to the system with the privileges of the affected account.
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 dataall versionsall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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.
-
List all local user accountsRun 'net user' at the command prompt to enumerate all local user accounts on the systemAffected if Any account exists that may have a weak or blank password
-
Check for accounts with blank passwordsFor each account returned, run 'net user [username]' and check whether the 'Password last set' field shows 'Never' or the account has no password indicator. In User Manager for Domains (NT) or Computer Management > Local Users and Groups (2000), examine each account and look for the 'Password not required' checkbox being enabled or the password field showing emptyAffected if Any local account has a blank password, shows 'Password last set: Never', or has 'Password not required' enabled
-
Examine the built-in Administrator accountCheck the default Administrator account (typically SID ending in -500) by running 'net user Administrator' or viewing it in User Manager. Verify whether it has a password set or if the password field is blank/emptyAffected if The Administrator account has no password set or uses a default blank password
-
Review password policy settingsRun 'net accounts' to display current password policy configuration. Check whether minimum password length is set to 0 and whether password complexity requirements are disabledAffected if Password policy allows blank passwords (minimum length of 0) or no complexity requirements are enforced
The system is affected if any local user or administrator account has a blank, null, or missing password, or if the password policy permits accounts without passwords.
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 dataAssign strong, unique passwords to all local user and administrator accounts, and disable or remove any accounts with blank or null passwords.
- 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-1999-0504 — 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-1999-0504 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