CVE-1999-1084: Medium severity Microsoft Windows NT vulnerability
The "AEDebug" registry key is installed with insecure permissions, which allows local users to modify the key to specify a Trojan Horse debugger which is automatically executed on a system crash.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Restrict the ACLs on the AEDebug registry key so local non-privileged users cannot modify it; allow only trusted/privileged accounts to change the debugger value.
Microsoft Windows NT (AEDebug registry key) permissions = prevent modification by local non-privileged users - Operational
Audit the AEDebug registry key for any unauthorized or unexpected 'debugger' values. If an untrusted or malicious debugger is configured, remove or correct the entry and investigate the host for compromise before restoring a trusted debugger setting.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-1084?
CVE-1999-1084 is considered a high severity vulnerability due to its potential to allow local users to execute malicious code.
How do I fix CVE-1999-1084?
To fix CVE-1999-1084, modify the permissions of the "AEDebug" registry key to restrict access to unauthorized users.
What software is affected by CVE-1999-1084?
CVE-1999-1084 affects Microsoft Windows NT 4.0 on both server and workstation versions.
What can attackers do with CVE-1999-1084?
Attackers can modify the "AEDebug" registry key to run a Trojan Horse debugger when the system crashes.
Is CVE-1999-1084 relevant to current systems?
CVE-1999-1084 is an older vulnerability primarily relevant to legacy systems running Windows NT 4.0.