Buffer overflows in Microsoft SQL Server 7.0 and SQL Server 2000

Overview

There is a buffer overflow in Microsoft SQL Server 2000 and SQL Server 7.0 which could allow an intruder to execute arbitrary code on vulnerable systems.

Description

Microsoft Windows SQL Server 2000 and SQL Server 7.0 contain a buffer overflow in functions associated with text messages. For more information, see

<http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS01-060.asp&gt;
<http://www.atstake.com/research/advisories/2001/index_q1.html&gt;

Quoting from MS01-060,

_The functions that contain the unchecked buffers are associated with creating, and in some cases displaying, text messages. SQL Server provides several functions that enable a database query to create formatted text. _

Intruders who can execute queries containing these functions can exploit a buffer overflow. An intruder who could load and execute queries of his own choosing would be able to exploit this vulnerability. Other intruders may be able to execute this vulnerability as well. Again, quoting from MS01-060,

_If the database search [or other routine] called one of the affected functions, it might be possible for an attacker to construct a query that would cause [an affected] function to be called in such a way as to exploit the vulnerability. Clearly, this would require intimate knowledge of the internals of the database query.

On the other hand, if the database query were poorly implemented, the attacker might not need to know its internal details in order to exploit the vulnerability. One frequently exploited implementation error occurs when a database query doesn’t adequately check its inputs before using them. In some cases, this would make it possible for an attacker to embed database commands – including, in this case, calls to the affected functions – within database query parameters. This underscores the need to always check input parameters before using them. _

Applying the patch protects against all these attack scenarios, though it is still wise to ensure that input parameters to SQL Server queries are closely examined to guard against other possible vulnerabilities or unauthorized access.

---

Impact

Intruders can execute arbitrary code with the privileges of the SQL server process.

---

Solution

Apply a patch as described in MS01-060.

---

Vendor Information

700575

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 __ Affected

Updated: December 21, 2001

Status

Affected

Vendor Statement

See <http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS01-060.asp&gt;.

Vendor Information

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

Addendum

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%23700575 Feedback>).

CVSS Metrics

Group	Score	Vector
Base
Temporal
Environmental

References

• <http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS01-060.asp&gt;
• <http://www.atstake.com/research/advisories/2001/index_q1.html&gt;
• <http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/confeat/c05ppcsq.asp&gt;
• <http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/maintain/security/sqlc2.asp&gt;
• <http://www.microsoft.com/Downloads/Release.asp?ReleaseID=35066&gt;
• <http://www.microsoft.com/Downloads/Release.asp?ReleaseID=35067&gt;
• <http://www.uniras.gov.uk/l1/l2/l3/brief2001/UNIRAS Briefing - 25001 - Microsoft - SQL Server Text Formatting Functions Contain unchecked Buffers (MS01-060).txt&gt;

Acknowledgements

Our thanks to Microsoft for the information contained in their bulletin. Microsoft has publicly thanked Chris Anley of @Stake for reporting this issue to them.

This document was written by Shawn V. Hernan.

Other Information

CVE IDs:	CVE-2001-0542
Severity Metric:	15.19 Date Public: