List of security fixes and improvements in Veeam Backup & Replication

This article describes all security-related fixes and improvements introduced in each release or update of Veeam Backup & Replication.

The goal of this article is to provide our customers' security and compliance teams with detailed information on security improvements between releases, in order to help them make an informed decision on whether it is critical to upgrade from their current Veeam Backup & Replication version to a latter one.

11.0.1.1261 P20220302

• Vulnerabilities (CVE-2022-26500, CVE-2022-26501) in Veeam Distribution Service were fixed.
  These vulnerabilities were reported by Nikita Petrov (Positive Technologies).
  
• Vulnerability (CVE-2022-26504) in Veeam.Backup.PSManager was fixed.
• Vulnerability (CVE-2022-26503) in Veeam Agent for Microsoft Windows was fixed.
  This vulnerability was reported by Nikita Petrov (Positive Technologies).
   

11.0.1.1261

• Linux data mover: Added support for ECDHE TLS cipher suites; improved transport security.
• Veeam Backup Enterprise Manager: hardened HTTP header configuration; disabled HTTP Trace method; restricted an ability to log into the Self-Service Restore Portal under NETWORK SERVICE accounts (the portal was dysfunctional for such logins).
• Helper appliances: updated OpenVPN to version 2.4.11; updated OpenSSH to version 8.6.
• Debug logs: Addressed issues which could result in sensitive information logged under certain circumstances.
   

11.0.0.837 P20210507

• Vulnerability (CVE-2021-35971) in the deserialization logic of Microsoft .NET remoting has been fixed.
   

11.0.0.837

• .NET remoting communication security has been improved.
  
• Data Mover communication protocol security has been improved.
• Agent Management architecture security has been improved.
• Veeam Explorers integration security has been improved
• Veeam Backup Enterprise Manager Web App configuration and headers security has been improved.
• Addressed issues which could cause sensitive information logged in certain circumstances.
• Third-party libraries in FLR and SureBackup helper appliance have been updated to current versions.
• Sustansys.Saml2 has been updated to version 2.7 to address known vulnerabilities.
• LZ4 compression library version has been updated to version 1.9.2
   

10.0.1.4854 P20220304

• Vulnerabilities (CVE-2022-26500, CVE-2022-26501) in Veeam Distribution Service were fixed.
  These vulnerabilities were reported by Nikita Petrov (Positive Technologies).
  
• Vulnerability (CVE-2022-26504) in Veeam.Backup.PSManager was fixed.
• Vulnerability (CVE-2022-26503) in Veeam Agent for Microsoft Windows was fixed.
  This vulnerability was reported by Nikita Petrov (Positive Technologies).
   

10.0.1.4854 P20210609

• Vulnerability (CVE-2021-35971) in the deserialization logic of Microsoft .NET remoting has been fixed.
   

10.0.1.4854

• NAS Backup functionality can be used to gain unprivileged access to files on managed servers.
• Weak credentials encryption issue in guest processing command line parameter and in PowerShell cmdlet logs.
• Server and IIS version information is included in the response header of the Veeam Backup Enterprise Manager web app.
• Security of Agent Management architecture has been improved.
• Security of Cloud Connect architecture has been improved.
• libcurl version has been updated to 7.70
   

10.0.0.4461

• A custom security descriptor was provided for the driver's control device (vulnerability reported by Mile Karry).
• Deserialization issues were fixed (vulnerability reported by Harrison Neal).
• A user authorization issue was fixed (vulnerability reported by Harrison Neal).
• Security of the Enterprise Manager Web App configuration was improved.
• Support for weak SSH ciphers was disabled in the recovery media ISOs.
• OpenSSL library was updated to version 1.0.2t
• Putty was updated to version 0.73
• Weak TLS ciphers were disabled in the Surebackup Linux appliance.

As we're establishing this new process, we appreciate any feedback on the content or format of this KB article. Please let us know in the corresponding topic on the Veeam Community Forums. If your feedback is too sensitive to be shared publicly, please submit it by opening a support case. We highly appreciate your collaboration!