Attributed metadata history

ClamAV 1.2.0 feature version and 1.1.2, 1.0.3, 0.103.10 patch versions published

The ClamAV 1.2.0 feature release is now stable and available for download on the ClamAV downloads page, on the Github Release page, and through Docker Hub.Today, we are also publishing the 1.1.2, 1.0.3, and 0.103.10 security patch versions. You may be surprised about the impromptu patch release. Indeed, we just published patch versions earlier this month. Unfortunately, a recent CVE for the UnRAR* library has prompted us to prepare these additional updates. We strongly encourage everyone to upgrade to one of these versions. The release files for the patch versions are also available for download on the ClamAV downloads page, on the Github Release page, and through Docker Hub. Because ClamAV 1.2.0 is now the latest release, the release files for version 1.1.2 will be found under the "Previous Stable Releases" section of the ClamAV.net downloads page.*UnRAR is an open source library by the makers of WinRAR which we bundle with ClamAV under the name "libclamunrar". We are concerned that ClamAV may be affected by CVE-2023-40477. Special thanks to Jan Pokorny, at St. Anne's University Hospital, for identifying its potential impact on ClamAV and reporting it to us.Continue reading to learn what changed in each version.1.2.0ClamAV 1.2.0 includes the following improvements and changes:Major changesAdded support for extracting Universal Disk Format (UDF) partitions.Specifically, this version adds support for the Beginning Extended Area Descriptor (BEA01) type of UDF files.GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/941Added an option to customize the size of ClamAV's clean file cache.Increasing the size of the clean file cache may improve scan performance but will require more RAM. The cache size value should be a square number or will be rounded up to the nearest square number.The cache size option for clamd and clamscan is --cache-size. Alternatively, you can customize the cache size for ClamD by setting CacheSize in clamd.conf.Patch courtesy of Craig Andrews.GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/882Introduced a SystemD timer for running Freshclam updates, without sending Freshclam into the background. This takes the "burden of timing the updates" from Freshclam and puts it onto SystemD. The timer can be activated, audited, and the logs inspected:sudo systemctl enable --now clamav-freshclam-once.timer sudo systemctl list-timers sudo systemctl status clamav-freshclam-once.timer sudo systemctl status clamav-freshclam-once.service journalctl -u clamav-freshclam-once.service If you want a different update interval you can edit the timer unit file:sudo systemctl edit clamav-freshclam-once.timer Patch courtesy of Nils Werner.GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/962Raised the MaxScanSize limit so the total amount of data scanned when scanning a file or archive may exceed 4 gigabytes.Introduced the ability to suffix the MaxScanSize and other config file size options with a "G" or "g" for the number of gigabytes. For example, for ClamD you may now specify MaxScanSize 10G in clamd.conf. And for ClamScan, you may now specify --max-scansize=10g.The MaxFileSize is still limited internally in ClamAV to 2 gigabytes. Any file, or embedded file, larger than 2GB will be skipped. You may use clamscan --alert-exceeds-max, or the clamd.conf option AlertExceedsMax yes to tell if a scan is not completed because of the scan limits.Patch courtesy of matthias-fratz-bsz.GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/945Added ability for Freshclam to use a client certificate PEM file and a private key PEM file for authentication to a private mirror by setting the following environment variables:FRESHCLAM_CLIENT_CERT: May be set to the path of a file (PEM) containing the client certificate.FRESHCLAM_CLIENT_KEY: May be set to the pa

This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.