Security readout for executives and security teams
Plain-English summary
On Windows NT, the login screen shows the username of the person who last signed in. That gives anyone with physical or remote console access half of the credentials they need to guess or brute-force an account. It is a hardening weakness, not a code flaw, and by default it exposes account names to anyone who walks up to a workstation or server console.
Executive priority
Low priority. Treat as configuration hygiene during standard hardening cycles, not an emergency. Elevate only if legacy Windows NT hosts still operate in the environment or if console-accessible systems handle sensitive accounts, since disclosed usernames make downstream password attacks easier.
Technical view
Windows NT's Winlogon caches and displays the last successful interactive username in the logon dialog. Sources describe this as a default configuration exposure rather than a memory-safety or privilege-escalation bug. Microsoft documented a registry setting (DontDisplayLastUserName under Winlogon) to suppress the value. No CVSS, CWE, or KEV entry is associated in the provided bundle, and no patch is required — remediation is a policy/registry change.
Likely exposure
Any legacy Windows NT host with default Winlogon settings that has a reachable console — physical, KVM, or remote desktop. Modern Windows fleets are unaffected unless administrators re-enabled the legacy behavior. Exposure is highest for kiosks, shared workstations, and domain controllers left at the logon screen.
Exploitation context
Not tracked in CISA KEV and no cited source claims active exploitation. The issue is information disclosure that assists credential-guessing or social-engineering campaigns; it is not directly exploitable for code execution. Attacker value comes from harvesting valid usernames at the console before attempting password attacks against them.
Researcher notes
The bundle carries no CVSS, CWE, or affected-product data, and the only reference is the IBM X-Force entry. Treat as a legacy hardening finding tied to Windows NT Winlogon defaults. Modern audits should map this to CIS/Microsoft baseline controls for 'Interactive logon: Do not display last user name' rather than a patchable CVE.
Mitigation direction
- Enable the 'Interactive logon: Do not display last user name' Group Policy on all affected hosts.
- Set HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\DontDisplayLastUserName = 1 where GPO is unavailable.
- Retire remaining Windows NT systems that cannot be hardened or centrally managed.
- Restrict physical and remote console access to logon screens on shared or exposed endpoints.
- Consult current Microsoft security baselines for the equivalent modern setting on supported Windows versions.
Validation and detection
- Lock the workstation and confirm the username field is blank on the logon dialog.
- Query the DontDisplayLastUserName registry value and confirm it is set to 1.
- Run 'gpresult /h' or 'rsop.msc' and verify the corresponding Interactive Logon policy is applied.
- Audit domain and local security policy baselines for drift from the hardened setting.
- Spot-check kiosks, RDP session hosts, and jump boxes since they are the highest-value console targets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-1999-0592 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://exchange.xforce.ibmcloud.com/vulnerabilities/1353CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.