Hello, welcome to the Monday, December 20th, 2021 edition of the Sansanet Storm Center's Stormcast. My name is Johannes Ulrich, and I'm recording from Jacksonville, Florida. Did you ever have to fail over to a secondary data center, maybe after a power outage or some kind of connectivity interruption to your primary data

center. Well, if you have ever been in that situation, you may appreciate Rob's post from

Friday where he goes over some of the options you have to automatically script some of the

DNS failover that often has to happen in this case.

I've used DNS to failover between data centers many times in the past.

I always liked it because it's relatively cheap and easy to do.

And these days, most of the cloud providers that you're likely using to host DNS do offer APIs to make this change

relatively easy. So Rob has some sample code for you. I've also noticed that there are a number

of like Python modules out there that make this kind of scripting easier for a different DNS providers and even some that sort of have

a generic basically API that then can be used with various cloud-based DNS providers.

And did he provide this weekend a quick update to an older diary of his that dealt with the version numbers that you're

finding in Visual Basic for application, office documents. Well, there's a new version number

for Microsoft Office version 2021. It's Bravo 5. Well, then we have more news from Log 4J and the Log 4G shell vulnerability.

The vulnerability just keeps on giving.

So I figured I'll go over some of the Log 4J version numbers that you may be encountering.

First, there was Log 4J 2.15. It's meant for Java 8 and it fixes the

original, if you want to call it this way, log for shell vulnerability with a CVSS score of 10

and a CVE number of 20, 21, 44, 22, 8.

This is still the vulnerability that you probably should worry about the most.

It's the easiest to exploit and the one that we see really sort of a lot of exploits for in the wild.

But turned out that the patch delivered with 2.15 was not sufficient then.

Shortly after, and this was already covered last week,

...