CVE-1999-0575
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 system's user audit policy does not log an event success or failure, e.g. for Logon and Logoff, File and Object Access, Use of User Rights, User and Group Management, Security Policy Changes, Restart, Shutdown, and System, and Process Tracking.
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 confidenceWindows NT's audit policy is not configured to log security events such as Logon/Logoff, File and Object Access, Use of User Rights, User and Group Management, Security Policy Changes, Restart, Shutdown, and System/Process Tracking. This means security-relevant activities go unrecorded, preventing detection of unauthorized access or malicious activities through log analysis.
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 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.
-
Verify audit policy is enabledOpen User Manager (usrmgr.exe) on the Windows NT system, then go to Policies > Audit to view the audit policy configuration. Alternatively, check the registry key HKLM\SECURITY\Policy\PolicyAccounts or use the 'auditpol' command if available.Affected if Audit policy is disabled or set to 'No Audit'
-
Check which security event categories are configuredIn User Manager > Policies > Audit, examine which event categories are enabled. The summary indicates the following categories should be logged: Logon/Logoff, File and Object Access, Use of User Rights, User and Group Management, Security Policy Changes, Restart, Shutdown, and System/Process Tracking.Affected if One or more of these critical security categories are not enabled for auditing
-
Verify security event logging is activeOpen Event Viewer and navigate to the Security log. Attempt to perform actions such as user logon/logoff, file access, or policy changes, then check if these events appear in the Security log.Affected if The Security log is empty or does not contain events from the categories listed above after performing typical operations
-
Confirm audit log is configured to retain recordsIn Event Viewer, check the Security log properties to verify maximum log size and retention settings. Also verify the log is not set to 'Do not overwrite' with full clearing, which could cause events to be lost.Affected if Audit logging is configured in a way that results in no persistent security event records
The system is affected if the Windows NT audit policy is disabled or not configured to log all specified security event categories, resulting in no security events being recorded in the Security log.
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 dataEnable and configure Windows NT audit policy to log all relevant security event categories including Logon/Logoff, Object Access, User Rights, User Management, Security Policy Changes, and System events.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0575 — 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-0575 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