#1 Global Leader in Data Resilience

Support Statement regarding Microsoft CVE-2023-24932

KB ID: 4452
Product: Veeam Agent for Microsoft Windows
Published: 2023-05-24
Last Modified: 2023-06-02
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

Microsoft recently released update KB5025885 containing changes to secure boot. These changes require specific actions to be taken to continue using Veeam Agent for Microsoft Windows bare metal recovery media and other restore operations. 

After applying the Microsoft Update with revocations described in KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932, the following will occur:

  • Any bootable media based on non-updated WinRE will fail to boot. Veeam Agent utilizes the Windows Recovery Environment (WinRE) in Veeam Recovery Media. 
  • Restoring a machine from an earlier restore point where KB5025885  is not installed will result in an OS boot failure after restore.

Solution

Issue 1 —  Outdated Recovery Media


New Deployments

No actions are required, as both the OS of the machine being backed up and WinRE will already have the necessary updates. (check MS for new ISO images)
 

Existing Deployments
  1. Install updates and inject KB5025885 into the WinRE.wim using the script documented in:
    KB5025175: Updating the WinRE partition on deployed devices to address security vulnerabilities in CVE-2022-41099
  2. After the WinRE has been updated, recreate the Recovery Media:
For backup jobs operating in Managed by backup server mode, an Active Full must be performed to force recollection of the updated Windows Recovery image.

Issue 2 — Restore from Older Restore Points Fails to Boot

The most straightforward workaround is to disable Secure Boot, which will allow the machine to boot. However, please consider all security implications documented in Microsoft Documentation: Disabling Secure Boot

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.