9 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:S/C:C/I:C/A:C
0.002 Low
EPSS
Percentile
56.9%
The default installation of WinVNC on certain Microsoft Windows systems permits unauthenticated access to the WinVNC service.
AT&T WinVNC is a free package available from AT&T Labs Cambridge that allows an existing desktop of a PC to be available on the desktop of a remote host. This software runs on Windows 95, Windows98, Windows NT 4.0, and Windows 2000. The default installation of WinVNC creates a registry key which is used to store some of WinVNC’s default settings. Some of these settings include the connection password as well as an IP based restriction list. The privileges on this registry key allow full access from the Administrator or System accounts and gives the “Everybody” group read and modify privileges. Upon creation, this key is insufficiently protected such that an attacker can modify the registry key values, which could allow unauthenticated access to the service. For example, an intruder could edit the registry and delete the value for the password field and set the key marked “AuthRequired” to 0. This would allow the intruder full access to the WinVNC service. It should be noted that on Windows 2000, network users with “Power User” privileges could edit the registry and delete the value for the password field as well. Ideally, only administrators should have access to the HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\ registry key.
This vulnerability could allow a remote attacker to modify the HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\ key and allow unauthenticated access to the service.
Use Regedit to remove the “Standard Users” & “Everybody” permissions from the HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\ registry key. Additionally, one should make sure that access to the registry is restricted to authorized personnel.
197477
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Updated: May 25, 2001
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23197477 Feedback>).
Group | Score | Vector |
---|---|---|
Base | ||
Temporal | ||
Environmental |
This vulnerability was discovered by Gossi The Dog and was reported to the Bugtraq mailing list on December 11, 2000.
This document was written by Ian A. Finlay.
CVE IDs: | CVE-2000-1164 |
---|---|
Severity Metric: | 4.70 Date Public: |