Microsoft SQL Server service account registry key has weak permissions that permit privilege escalation

Overview

The Microsoft SQL Server contains a vulnerability that allows remote attackers to execute arbitrary commands with system privileges.

Description

The Microsoft SQL Server typically runs under a dedicated “service account” that is defined by system administrators at installation time. This definition is stored in the Windows registry with permissions that allow the SQL Server to change the value of the registry key. As a result, attackers with access to the “xp_regwrite” extended stored procedure can alter this registry key and cause the SQL Server to use the LocalSystem account as its service account. Upon rebooting the server host or restarting the SQL service, the SQL Server will run with the full administrative privileges of the LocalSystem account. This ability allows a remote attacker to submit SQL queries that can execute any command on the system with the privileges of the operating system.

---

Impact

As a precondition, this vulnerability requires the ability to modify the SQL service account registry key (for example, via the “xp_regwrite” extended stored procedure). Attackers must convince an administrator to grant this access, or they must obtain it by exploiting a second vulnerability.

This vulnerability allows attackers to weaken the security policy of the SQL Server by elevating its privileges and causing it to run in the LocalSystem security context. As a side effect, it increases the severity of vulnerabilities that allow attackers to gain the privileges of the SQL service account. In some cases, this may enable attackers to compromise the server host as well.

---

Solution

Apply a patch

Microsoft has published Security Bulletin MS02-034 to address this vulnerability. For more information, please see

http://www.microsoft.com/technet/security/bulletin/MS02-034.asp

This vulnerability also affects any products that include the Microsoft Desktop Engine (MSDE) 2000. For more information, please see

http://www.microsoft.com/technet/security/MSDEapps.asp

---

Vendor Information

796313

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.

Microsoft Corporation __ Affected

Notified: April 24, 2002 Updated: July 25, 2002

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Microsoft has published Security Bulletin MS02-034 to address this vulnerability. For more information, please see

http://www.microsoft.com/technet/security/bulletin/MS02-034.asp

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23796313 Feedback>).

CVSS Metrics

Group	Score	Vector
Base
Temporal
Environmental

References

• <http://www.microsoft.com/technet/security/bulletin/MS02-034.asp&gt;
• <http://www.microsoft.com/technet/security/MSDEapps.asp&gt;
• <http://support.microsoft.com/support/misc/kblookup.asp?id=Q316333&gt;
• <http://www.microsoft.com/technet/prodtechnol/sql/maintain/security/sql2ksec.asp&gt;
• <http://www.securityfocus.com/bid/5205&gt;

Acknowledgements

This vulnerability was discovered by Bronek Kozicki and reported to the Bugtraq mailing list on April 18, 2002.

This document was written by Jeffrey P. Lanza and is based upon information provided by Microsoft.

Other Information

CVE IDs:	CVE-2002-0642
CERT Advisory:	CA-2002-22 Severity Metric: