Operational Defect Database
BugZero found this defect 1540 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb3109
List of Security Fixes and Improvements in Veeam Agent for Linux
Last update date:
3/13/2024
Affected products:
Veeam Agent for Linux
Affected releases:
5.0
Fixed releases:
No fixed releases provided.
Description:
Purpose
This article describes all security-related fixes and improvements introduced in each release or update of Veeam Agent for Linux. The goal of this article is to provide our customers' security and compliance teams with the 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 Agent for Linux version to a latter one.
Security Fixes and Improvements
6.1.0.1498 OpenSSL library updated to 1.0.2zi. LZ4 library updated to 1.9.4. Updated zlib library to 1.2.13. Stronger backup encryption. - (See pg. 7 of Veeam Backup & Replication 12.1 What's New PDF) 6.0.2.1168 OpenSSL Library updated to the newest version (1.0.2zg). 5.0.2.4707 OpenSSL was updated to v1.0.2zi. liblz4 was updated to v1.9.4. zlib was updated to v1.2.13. PuTTY was updated to 0.80. 5.0.0.4318 Addressed an issue with insecure default permissions of files created in /tmp LZ4 compression library version has been updated to version 1.9.2. 4.0.1.2365 Sensitive information used by managed Linux agent may get logged in the Linux operating system logs. Creating an SMB repository using CLI command causes plain text password to be logged in the Veeam debug log. 4.0.0.1961 An issue of insecure file permissions was addressed (vulnerability reported by RACK911 Labs). OpenSSL was updated to version 1.0.2t.
More Information
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!
