Wednesday, October 25, 2023

ClamAV 1.2.1, 1.1.3, 1.0.4, 0.103.11 patch versions published

Today, we are publishing the 1.2.1, 1.1.3, 1.0.4, and 0.103.11 security patch versions.

The release files for the patch versions are available for download on the ClamAV downloads page, on the GitHub Release page, and through Docker Hub.

Continue reading to learn what changed in each version.

1.2.1

ClamAV 1.2.1 is a patch release with the following fixes:

Special thanks to Yasuhiro Kimura for code contributions and bug reports.

1.1.3

ClamAV 1.1.3 is a patch release with the following fixes:

Special thanks to Yasuhiro Kimura for code contributions and bug reports.

1.0.4

ClamAV 1.0.4 is a patch release with the following fixes:

Special thanks to Yasuhiro Kimura for code contributions and bug reports.

0.103.11

ClamAV 0.103.11 is a patch release with the following fixes:


Posted by at
Labels: , , , , , , ,

Monday, August 28, 2023

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.0

ClamAV 1.2.0 includes the following improvements and changes:

Major changes

  • Added support for extracting Universal Disk Format (UDF) partitions.

    Specifically, this version adds support for the Beginning Extended Area Descriptor (BEA01) type of UDF files.

  • Added 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.

  • Introduced 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.

  • Raised 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.

  • Added 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 path of a file (PEM) containing the client private key.
    • FRESHCLAM_CLIENT_KEY_PASSWD: May be set to a password for the client key PEM file, if it is password protected.

    Patch courtesy of jedrzej.

Other improvements

  • Fix an issue extracting files from ISO9660 partitions where the files are listed in the plain ISO tree and there also exists an empty Joliet tree.

  • CMake build system improvement to support compiling with OpenSSL 3.x on macOS with the Xcode toolchain.

    The official ClamAV installers and packages are now built with OpenSSL 3.1.1 or newer.

  • The suggested path for the clamd.pid and clamd.sock file in the sample configs have been updated to reflect the recommended locations for these files in the Docker images. These are:

    • /run/clamav/clamd.pid
    • /run/clamav/clamd.sock

    For consistency, it now specifies clamd.sock instead of clamd.socket.

    Patch courtesy of computersalat.

Bug fixes

Acknowledgments

Special thanks to the following people for code contributions and bug reports:

  • computersalat
  • Craig Andrews
  • jedrzej
  • matthias-fratz-bsz
  • Nils Werner
  • Răzvan Cojocaru

1.1.2

ClamAV 1.1.2 is a critical patch release with the following fixes:


1.0.3

ClamAV 1.0.3 is a critical patch release with the following fixes:


0.103.10

ClamAV 0.103.10 is a critical patch release with the following fixes:


Posted by at
Labels: , , , , , ,

Tuesday, August 15, 2023

ClamAV 1.1.1, 1.0.2, 0.103.9 patch versions published

Today, we are releasing the following critical patch versions for ClamAV: 

  • 1.1.1 
  • 1.0.2 
  • 0.103.9 

 

ClamAV 0.105 and 0.104 have reached end-of-life according to the ClamAV’s End of Life (EOL) policy and will not be patched.


The release files are available for download on ClamAV.net, on the Github Release page, and through Docker Hub.


Note: We observed an issue building ClamAV on Windows using the recently released libjson-c version 0.17. If you are building ClamAV for Windows, you should use libjson-c version 0.16 or prior.


1.1.1 

ClamAV 1.1.1 is a critical patch release with the following fixes: 


  • CVE-2023-20197 Fixed a possible denial of service vulnerability in the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through 1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8 through 0.103.0. Thank you to Steve Smith for reporting this issue. 
  • Fixed a build issue when using the Rust nightly toolchain, which was affecting the oss-fuzz build environment used for regression tests.
  • Fixed a build issue on Windows when using Rust version 1.70 or newer. 
  • CMake build system improvement to support compiling with OpenSSL 3.x on macOS with the Xcode toolchain. The official ClamAV installers and packages are now built with OpenSSL 3.1.1 or newer. 
  • Removed a warning message showing the HTTP response codes during the Freshclam database update process. 

 

Special thanks to the following people for code contributions and bug reports: 

  • Steve Smith 

 

1.0.2 

ClamAV 1.0.2 is a critical patch release with the following fixes: 


  • CVE-2023-20197 Fixed a possible denial of service vulnerability in the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through 1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8 through 0.103.0. Thank you to Steve Smith for reporting this issue. 
  • CVE-2023-20212 Fixed a possible denial of service vulnerability in the AutoIt file parser. This issue affects versions 1.0.1 and 1.0.0. This issue does not affect version 1.1.0. 
  • Fixed a build issue when using the Rust nightly toolchain, which was affecting the oss-fuzz build environment used for regression tests. 
  • Fixed a build issue on Windows when using Rust version 1.70 or newer.
  • CMake build system improvement to support compiling with OpenSSL 3.x on macOS with the Xcode toolchain. The official ClamAV installers and packages are now built with OpenSSL 3.1.1 or newer. 
  • Fixed an issue where ClamAV does not abort the signature load process after partially loading an invalid signature. The bug would later cause a crash when scanning certain files. 
  • Fixed an issue so that ClamAV correctly removes temporary files generated by the VBA and XLM extraction modules so that the files are not leaked in patched versions of ClamAV where temporary files are written directly to the temp-directory instead of writing to a unique subdirectory.
  • Set Git attributes to prevent Git from altering line endings for bundled Rust libraries. Third-party Rust libraries are bundled in the ClamAV release tarball. We do not commit them to our own Git repository, but community package maintainers may now store the tarball contents in Git. The Rust build system verifies the library manifest, and this change ensures that the hashes are correct. Improvement courtesy of Nicolas R. 
  • Fixed two bugs that would cause Freshclam to fail update when applying a CDIFF database patch if that patch adds a file to the database archive or removes a file from the database archive. This bug also caused Sigtool to fail to create such a patch. 

 

Special thanks to the following people for code contributions and bug reports: 

  • Nicolas R. 
  • Steve Smith 

 

 

0.103.9 

ClamAV 0.103.9 is a critical patch release with the following fixes: 


  • CVE-2023-20197 Fixed a possible denial of service vulnerability in the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through 1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8 through 0.103.0. Thank you to Steve Smith for reporting this issue. 
  • Fixed compiler warnings that may turn into errors in Clang 16. Patch courtesy of Michael Orlitzky.

 

Special thanks to the following people for code contributions and bug reports: 

  • Michael Orlitzky 
  • Steve Smith 

 

Posted by at
Labels: , , , , ,
Subscribe to: Posts ( Atom )