CVE-1999-0577
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 file audit policy does not log an event success or failure for non-critical files or directories.
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 file audit policy fails to log success or failure events for non-critical files and directories, creating a security monitoring gap where unauthorized access attempts to these assets go unrecorded and undetected.
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
- 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.
-
Verify file access auditing is enabled in Security PolicyOpen User Manager or Policy Editor, navigate to Policies > Audit, and check if 'File and Object Access' auditing is enabledAffected if File and Object Access auditing is not enabled or is completely absent from the audit policy
-
Confirm success audit events are configured for file accessIn the same Audit Policy section, verify that 'File and Object Access' includes success auditing enabledAffected if Success audit events for file/object access are not enabled
-
Confirm failure audit events are configured for file accessIn the same Audit Policy section, verify that 'File and Object Access' includes failure auditing enabledAffected if Failure audit events for file/object access are not enabled
-
Identify which files and directories have explicit auditing configuredUse the Security menu in Windows Explorer or the auditpol command (if available) to view the audit entries on specific files and folders, or check the System Access Control List (SACL) on critical directoriesAffected if No files or directories have auditing configured, or only a limited set of 'critical' files have auditing while non-critical files do not
The environment is affected if file and object access auditing is disabled, or if success/failure auditing for file access is not enabled, or if critical files/directories lack audit entries in the SACL.
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 dataConfigure Windows NT Security Policy to enable object access auditing for file system objects, specifically enabling both success and failure audit events for critical files and directories.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0577 — 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-0577 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