Nice to see they patched this one.  Have deployed in my homelab without issues.

I checked KB4245, and the build number does not match the email.

It should be 11.0.1.1261 P20220302, not P20230227. It seems the same as last year's release.

@CarySun The KB article hadn't been updated until now and did show the old build number. I'll update my post.

I checked KB4245, and the build number does not match the email.

It should be 11.0.1.1261 P20220302, not P20230227. It seems the same as last year's release.

 

Thank you.
I forwarded the feedback. We will update it.

These are the correct KBs.

V11a: https://www.veeam.com/kb4424

V12: https://www.veeam.com/kb4420

Nice! Veeam corrected the KB4245 contents.

Nice! Veeam corrected the KB4245 contents.

 

Yeah I have been watching the KBs so nice to see the change.

Another round of upgrades..

Hi,

Bit confused about the different versions. I’m in the process of pathcing my v11a, after patching can you please tell me exactly what the version on the help=>about should read that i know it is the patched one and i’m all good to go ?

thanks

Hi Vassilis, for v11 build number will be 11.0.1.1261 P20230227

https://www.veeam.com/kb4245

If you are upgrading to v12, the version will be 12.0.0.1420 P20230223

https://www.veeam.com/kb4420

Thanks marco,

So i’m good ??? i have nothing to be fear off, let the hackers try 

Looks good, so at least you don't have to fear this certain vulnerability anymore

First patching

Patching v12 is all good in my homelab no issues.  Patch planning for our v11a environment is now in progress before we upgrade to v12.  

Hello everybody,

I’m having issues with one of the v11 installations after applying the patch, with errors like:

Failed to preprocess target Error: Field not found: 'Veeam.Backup.Common.COptions.RetrieveCertUseTls12Only'.  

Patching on other infrastructures (both v11 and v12) went smoothly.

Anyone else experiencing the same behaviour?

ΤΥη

The error says about tls1.2 , mayb your specific server does not allow tls 1.2, can you check with crypto and see the protocols enabled around your B&R infra.

I would strongly suggest to open a support ticket though.

Thank you @Vassilis, already opened SR #05922394 with high Severity.

Of course needless to say that this infrastructure worked correctly before the patch was applied, and that no other change was introduced in the meanwhile (I also refrained from applying a couple OS updates pending, that are already scheduled for next week).

Seems like somethings’ awry on the DB (“Field not found”…?!).

I am guessing it is not the SSL expired by chance.  Since the error RetrieveCertUseTls12Only has that in it.  Hopefully support gets it sorted out for you.

Silly question here:

After apply patch on v11, if I update VBR to V12…

Need I apply patch again?

Hello @wolff.mateus,

no you don’t if you used the already-updated ISO for the upgrade.

The KB4424 specifies:
All new deployments of Veeam Backup & Replication versions 12 and 11 installed using the ISO images dated 20230223 (V12) and 20230227 (V11) or later are not vulnerable.

I am going to assume the ISO for v12 will include the patch like they did with v11a.  So, the upgrade should have the patch.

Thank you @Chris.Childerhose,

support refers of a known issue with v11 that I’ve incurred into, and at first recommends upgrading to v12 (which can’t currently be done due to missing Azure plug-in for v12).

It depends when you downloaded the ISO for V12, it if was before yesterday you will need to download the patch. https://www.veeam.com/kb4420

I just finished a project and I already have to patch it! Glad to see the responsiveness of Veeam to fix this vulnerability

I also today updated environments, which I had upgraded just last week. That’s life

@pgallenga Where do you get this error?