#1 Global Leader in Data Resilience

Security Issue in Microsoft Azure Plug-In for Veeam Backup & Replication

KB ID: 4491
Product: Veeam Backup & Replication | 12
Published: 2023-09-07
Last Modified: 2023-09-07
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.

Issue Details

This article highlights a security-related issue in Microsoft Azure Plug-In for Veeam Backup & Replication 12.1.5.99 that may allow a user accessing the Veeam Backup & Replication server to obtain the administrator credentials of the Veeam Backup for Microsoft Azure backup appliance, potentially allowing an attacker to gain access to the Veeam Backup for Microsoft Azure appliance.

This issue explicitly affects any environment where an existing deployment of Veeam Backup for Microsoft Azure was upgraded to version 5a while using Microsoft Azure Plug-In for Veeam Backup & Replication version 12.1.5.99. During the appliance upgrade process, administrator credentials were requested to update the Veeam Backup for Microsoft Azure backup appliance's operating system from Ubuntu 18.04 LTS to Ubuntu 22.04 LTS. That Veeam Backup for Microsoft Azure backup appliance administrator password was stored in the Updater log file: C:\ProgramData\Veeam\Backup\Plugins\Microsoft Azure\Logs\<backup_appliance_name>\Veeam.Azure.Updater.

Solution

To address this issue, Veeam has released a new build of Microsoft Azure Plug-In for Veeam Backup & Replication.

It is advised to install this update as soon as possible.

Issue fixed starting in: Microsoft Azure Plug-In for Veeam Backup & Replication 12.1.5.106

Update Procedure

  1. Obtain Microsoft Azure Plug-In for Veeam Backup & Replication 12.1.5.106.
  2. Uninstall Microsoft Azure Plug-In for Veeam Backup & Replication 12.1.5.99.
  3. Install Microsoft Azure Plug-In for Veeam Backup & Replication 12.1.5.106.
  4. Update the password for the account used by Veeam Backup & Replication to connect to Veeam Backup for Microsoft Azure.
    1. Update the password in Veeam Backup for Microsoft Azure first.
    2. Then, update the password within Veeam Backup & Replication.

When version 12.1.5.106 of the Plug-In is installed, the Plug-In will replace the backup appliance administrator password in the existing updater log files with asterisks (*). During future update procedures, the Plug-In will log only asterisks (*) instead of the actual Veeam Backup for Microsoft Azure backup appliance administrator password.

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.