Roll-up Patch Issued for SQL Server

Microsoft created a new cumulative patch for SQL Server 7.0 and SQL Server 2000.

A fix for a new flaw involving extended stored procedures in SQL Server 7.0 and SQL Server 2000 prompted Microsoft to roll up all the recent SQL Server patches. The new vulnerability rates as a moderate threat on Microsoft's security threat scale, but Redmond has kept SQL Server administrators hopping over the last month.

Bulletin MS02-043, issued late last week, contains the first SQL Server patch for August. But in July, database administrators saw five separate security bulletins dealing with SQL Server, including a cumulative patch early in that month.

The newly reported problem with SQL Server involves weak permissions with some of the extended stored procedures Microsoft's ships with SQL Server 7.0 and SQL Server 2000. Microsoft defines extended stored procedures as external routines written in a programming language such as C or C#. Some of the extended stored procedures shipped by Microsoft can reconnect to the database as the SQL Server service account, which in some cases could allow an attacker to run procedures on the server with administrative privileges.

The bulletin and patch can be found here:

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.


  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus