CVE-2002-1933
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 terminal services screensaver for Microsoft Windows 2000 does not automatically lock the terminal window if the window is minimized, which could allow local users to gain access to the terminal server window.
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 confidenceThe terminal services screensaver in Microsoft Windows 2000 fails to automatically lock the terminal session when the window is minimized. This allows a local user with physical access to the terminal server to view and interact with an unlocked session that the previous user thought was protected by the screensaver lock.
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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 the Windows versionOpen System Properties (right-click My Computer > Properties) or run 'winver' command. Check if the OS is Microsoft Windows 2000.Affected if The system is not Windows 2000 (this vulnerability only affects Windows 2000 Terminal Services)
-
Verify Terminal Services is installed and runningOpen Services (services.msc) and check if 'Terminal Services' service exists and is running, or check Computer Management > Services and Applications > Terminal Services.Affected if Terminal Services is not installed or not running on the system
-
Confirm Terminal Services is enabledOpen Control Panel > Add/Remove Programs > Add/Remove Windows Components > check if Terminal Services is enabled, or check the Terminal Services Configuration tool.Affected if Terminal Services is not enabled on the system
-
Examine screensaver lock behavior for minimized sessionsConnect via Terminal Services, configure a password-protected screensaver, minimize the Terminal Services window, and observe whether the session automatically locks after the screensaver timeout.Affected if The session remains accessible without authentication when the Terminal Services window is minimized, despite the screensaver being configured with password protection
A system is affected if it is running Windows 2000 with Terminal Services enabled, and the terminal session does not automatically lock when the Terminal Services window is minimized while a password-protected screensaver is active.
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 terminal services to require session locking even when minimized, or implement additional physical access controls at the terminal server location.
- 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-2002-1933 — 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-2002-1933 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