CVSS2
Attack Vector
LOCAL
Attack Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:L/AC:L/Au:S/C:P/I:P/A:P
EPSS
Percentile
32.5%
Microsoft Windows access controls may be improperly configured potentially allowing a local attacker to gain elevated privileges on a vulnerable system.
Microsoft Windows provides numerous, fine grained permissions and privileges to control access to Windows components, such as services, files, and registry entries.
Recent research has uncovered insecure configurations within user accounts and groups on Microsoft Windows systems. These configurations may allow local attackers to gain access to, and manipulate system resources. The researchers have developed a model that analyzes permissions to expose privilege escalation vulnerabilities. The research focused on three particular components of the Windows architecture:
Services
Windows services may be installed and configured with unnecessary privileges. This may allow a lesser privileged user to access and change the settings for a service that runs with greater privileges. Of particular concern are the following privileges:
The SERVICE_CHANGE_CONFIG
access right allows a user to change the a service’s configuration. This includes the executable that services launches and the user account with which a service runs as. According to Microsoft, “Because this grants the caller the right to change the executable file that the system runs, it should be granted only to administrators.”
The SERVICE_ALL_ACCESS
access right allows a user full control over a service.
Files and Directories
Any privileges that allow the contents of a file or a directory to be modified should be granted to only trusted users. The following access rights a of particular concern:
The FILE_ALL_ACCESS
access right allows a user to completely control a file, including read, write and execute privileges.
The FILE_APPEND_DATA
access right allows a user to add data to a file.
The FILE_WRITE_DATA
access right allows a user to write and rewrite data to a file.
Registry Keys
Users with KEY_SET_VALUE
permissions can modify registry keys that specify executables, DLLs, and/or Globally Unique Identifiers (GUIDs).
The WRITE_DAC
access right provides the ability to modify the access control list for a resource. Users granted this right have the ability to change the way they, or other users, access a resource. This may allow attackers to grant themselves, or others arbitrary permissions over a resource.
Note that these issues can affect all software that is developed for the Microsoft Windows platform. Known Windows services that have weak permissions include, but may not belimited to
* Microsoft SSDP Discovery service (`SSDPSRV`)
* NetBios over TCP/IP service (`NetBT`)
* Smart Card service (`SCardSvr`)
* Universal Plug and Play Device Host service (`upnphost`)
* DNS Client service (`Dnscache`)
* DHCP Client service (`Dhcp`)
A local user with valid login credentials may be able gain elevated privileges on a vulnerable Windows system.
We are aware of publicly available exploit code that claims to be a tool to identify vulnerable services. Installing and running this code may allow a remote attacker to gain access to a system.
These issues are corrected in Service Pack 2 for Microsoft Windows XP and Service Pack 1 for Microsoft Windows Server 2003. In addition, Microsoft Security Advisory 914457 and Microsoft Security Bulletin MS06-011 contain numerous workarounds to mitigate these vulnerabilities.
953860
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.
Notified: November 28, 2005 Updated: February 08, 2006
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Please see <http://www.adobe.com/support/techdocs/332644.html>.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23953860 Feedback>).
Notified: November 29, 2005 Updated: February 08, 2006
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Please see <http://www.macromedia.com/devnet/security/security_zone/mpsb05-04.html>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23953860 Feedback>).
Notified: November 28, 2005 Updated: February 08, 2006
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Please see <http://www.microsoft.com/technet/security/advisory/914457.mspx>.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23953860 Feedback>).
Notified: December 14, 2005 Updated: February 09, 2006
Not Affected
None of our products are vulnerable to this issue
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: April 21, 2006
Not Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Not Affected
We have investigated this issue, and determined that Oracle products are not vulnerable.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: November 28, 2005 Updated: February 08, 2006
Unknown
AOL is in the process of evaluating the research findings as they relate to installations of AOL software.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
As of yet, we have been unable to find any indication that our VShell product is affected by the privilege escalation issues described. We will continue to investigate the issue and provide any updates to the applicability of this vulnerability to our VShell product as they become available.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: December 14, 2005 Updated: February 08, 2006
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
View all 43 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | ||
Temporal | ||
Environmental |
These vulnerabilities were reported by Sudhakar Govindavajhala and Andrew W. Appel.
This document was written by Jeff Gennari.
CVE IDs: | CVE-2006-0023 |
---|---|
Severity Metric: | 4.22 Date Public: |
msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_security_and_access_rights.asp
msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/file_security_and_access_rights.asp
support.microsoft.com/?id=914392
www.cs.princeton.edu/~sudhakar/papers/winval.pdf
www.microsoft.com/technet/security/advisory/914457.mspx
www.microsoft.com/technet/security/Bulletin/MS06-011.mspx