Vulnerability Note VU#635463
Microsoft SQL Server and Microsoft Data Engine (MSDE) ship with a null default password
Microsoft SQL Server and Microsoft Data Engine ship with a null default password on the administrative account sa. If the system administrator does not set the password, the system may be vulnerable to attack.
Microsoft SQL Server (MS SQL) and Microsoft Data Engine (MSDE) ship without a default password on the administrative account sa, permitting unauthorized access via port 1433 TCP/UDP. As long as the server has a null password, gaining access to the sa account is trivial. While it may not be enabled under a default configuration, MSDE ships as a component of several applications such as Microsoft Office 2000 and Tumbleweed's Secure Mail (MMS). Tumbleweed's Secure Mail (MMS) Releases 4.3, 4.5, and 4.6 all ship with MSDE enabled and are vulnerable under the default configuration. A patch has been released to address this vulnerability on these versions of MMS and incorporated into the release of 4.7.
If the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer is defined, then you have MS SQL Server or MSDE installed. You should check to see if the sa account exists and ensure that a password is set. Instructions to change the password are located at
Through the use of various procedures such as xp_cmdshell(), an attacker can execute arbitrary commands on the system with whatever user privileges the Microsoft SQL services are running under. This is typically a user with "NT Authority\System".
Set a password for your SQL Server on the sa adminitration account.
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Microsoft Corporation||Affected||26 Nov 2001||27 Nov 2001|
|Tumbleweed||Affected||-||27 Nov 2001|
CVSS Metrics (Learn More)
This document was written by Jason Rafail.
- CVE IDs: Unknown
- Date Public: 10 Aug 2000
- Date First Published: 27 Nov 2001
- Date Last Updated: 20 Jun 2002
- Severity Metric: 33.75
- Document Revision: 30
If you have feedback, comments, or additional information about this vulnerability, please send us email.