Running a SQL Server? Heads up! You need to install this month’s patches quickly

Topic

New Reply

I just saw a notification that the SQL Server security hole known as CVE-2020-0618 has been cracked. Per Kevin Beaumont: Ah bums, there’s an exploit f
[See the full post at: Running a SQL Server? Heads up! You need to install this month’s patches quickly]

2 users thanked author for this post.

Mr. Natural, jabeattyauditor

Reply | Quote

Replies

Dang! How are the rest of the February patches looking from a DEFCON standpoint? If I’m rolling out to our business critical servers it’d be convenient to approve the whole set if the green light is coming.

Reply | Quote

Follow @b’s advice below.

So far the major Feb patch problems are from the one that was yanked (more about that later) and the infernal race condition that causes the Feb Win10 1903/1909 cumulative update to resurface with a temporary profile.

1 user thanked author for this post.

StoopidMonkey

Reply | Quote

So which patch or set of patches address this issue specifically?  You’ve been posting about all the bugs with this months patches so I don’t want to create more problems than I solve.

Reply | Quote

[b]

There are five different updates depending on the version number of SQL Server.

Check the current SQL Server version number in the table: CVE-2020-0618 FAQ

Then download/install the appropriate update: CVE-2020-0618 Security Updates

• This reply was modified 5 years, 3 months ago by b.

2 users thanked author for this post.

techweenie, woody

Reply | Quote

As a SQL DBA this is not good news. For SQL 2012/2014 the fixes could well be the last publicly released builds but SQL 2016 is expecting a Cumulative Update any day soon that should also include this fix.

1 user thanked author for this post.

woody

Reply | Quote