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: , , , , ,

Friday, August 4, 2023

ClamAV 1.2.0 release candidate now available

We are excited to announce the ClamAV 1.2.0 release candidate.

You may find the source code and installers for this release on the clamav.net/downloads page or the ClamAV GitHub release page.

Tip: If you are downloading the source from the GitHub release page, the package labeled "clamav-1.2.0-rc.tar.gz" does not require an internet connection to build. All dependencies are included in this package.  But if you download the ZIP or TAR.GZ generated by GitHub, located at the very bottom, then an internet connection will be required during the build to download additional Rust dependencies.

For Docker users, there is no specific Docker tag for the release candidate, but you can use the clamav:unstable or clamav:unstable_base tags.

The release candidate phase is expected to last two to three weeks before we publish the stable release or a second release candidate. Please take this time to evaluate ClamAV 1.2.0.  

Please help us validate this release by providing feedback via the ClamAV mailing list or on our Discord. 

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
Posted by at
Labels: ,

Friday, June 9, 2023

Shutting down old ClamAV Bugzilla

ClamAV will shut down the old ClamAV Bugzilla server in July.  

Users who have any outstanding Bugzilla reports should move them to GitHub Issues as soon as possible.

We disabled new tickets in Bugzilla in December 2021 in favor of GitHub Issues for all new ClamAV bug reports and a new process for reporting vulnerabilities as defined by a new security policy. As it has now been 18 months since the switch to GitHub Issues, we have decided to shut down our old Bugzilla.  

We plan to take the Bugzilla server off the internet sometime after July 1 and keep it as an internal reference for our development team. It will no longer be accessible to the public. 

Posted by at
Labels: ,

Monday, May 8, 2023

End of life (EOL) policy change, 0.103 one year extension, 0.105 past end of life

End of life (EOL) policy change 

ClamAV is making a minor change to our EOL policy. 

The original EOL policy stated that Long Term Support (LTS) versions will lose access to signature updates on the same date that we end support for additional patch versions. 

We are changing the policy to allow signature updates for at least one year after we stop supporting the release with patch versions. 

0.103 support extension 

We are also announcing a one-year extension of support for ClamAV 0.103 LTS. 

We decided to extend the life of the 0.103 LTS release because of the significant changes to the build system in 0.104 and the change in 0.105 requiring the Rust programming language toolchain to compile ClamAV. 

The one-year support extension does not apply to future LTS releases. 

ClamAV 0.103.0 was initially released on Sept. 14, 2020. With the additional year of support, and considering the change in the EOL Policy that allows one additional year of access for signature updates, this means that EOL dates for ClamAV 0.103 LTS are as follows: 
  • Expected End of Life (EOL): Sept. 14, 2024 
  • Patch versions continue until: Sept. 14, 2024 
  • Internal signature load testing until: Sept. 14, 2024 
  • Database downloads allowed until: Sept. 14, 2025 

0.105 EOL 

Finally, we would like to remind everyone that as per the EOL Policy, the release of ClamAV 1.1 heralds the end of patch versions supporting ClamAV 0.105. There will no more patch versions for ClamAV 0.105.

ClamAV 0.105 will continue to have access to signature updates for an additional four months after the 1.1 release, which was on May 1, 2023. This means that we may block 0.105 from further updates after Sept. 1, 2023. 

Posted by at
Labels: , , ,

Monday, May 1, 2023

ClamAV 1.1.0 released

The ClamAV 1.1.0 feature release is now stable and available for download on ClamAV.net or through Docker Hub.  

ClamAV 1.1.0 includes the following improvements and changes.


Major changes

  • Added the ability to extract images embedded in HTML CSS <style> blocks.

  • Updated to Sigtool so that the --vba option will extract VBA code from Microsoft Office documents the same way that libclamav extracts VBA. This resolves several issues where Sigtool could not extract VBA. Sigtool will also now display the normalized VBA code instead of the pre-normalized VBA code.

  • Added a new ClamScan and ClamD option: --fail-if-cvd-older-than=days. Additionally, we introduce FailIfCvdOlderThan as a clamd.conf synonym for --fail-if-cvd-older-than. When passed, it causes ClamD to exit on startup with a non-zero return code if the virus database is older than the specified number of days.

  • Added a new function cl_cvdgetage() to the libclamav API. This function will retrieve the age in seconds of the youngest file in a database directory, or the age of a single CVD (or CLD) file.

  • Added a new function cl_engine_set_clcb_vba() to the libclamav API. Use this function to set a cb_vba callback function. The cb_vba callback function will be run whenever VBA is extracted from office documents. The provided data will be a normalized copy of the extracted VBA. This callback was added to support Sigtool so that it can use the same VBA extraction logic that ClamAV uses to scan documents.

Other improvements

  • Removed the vendored TomsFastMath library in favor of using OpenSSL to perform "big number"/multiprecision math operations. Work courtesy of Sebastian Andrzej Siewior.

  • Build system: Added CMake option DO_NOT_SET_RPATH to avoid setting RPATH on Unix systems. Feature courtesy of Sebastian Andrzej Siewior.

  • Build system: Enabled version-scripts with CMake to limit symbol exports for libclamav, libfreshclam, libclamunrar_iface, and libclamunrar shared libraries on Unix systems, excluding macOS. Improvement courtesy of Orion Poplawski and Sebastian Andrzej Siewior.

  • Build system: Enabled users to pass in custom Rust compiler flags using the RUSTFLAGS CMake variable. Feature courtesy of Orion Poplawski.

  • Removed a hard-coded alert for CVE-2004-0597. The CVE is old enough that it is no longer a threat and the detection had occasional false-positives.

  • Set Git attributes to prevent Git from altering line endings for Rust vendored 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 compile time warnings. Improvement courtesy of Răzvan Cojocaru.

  • Added a minor optimization when matching domain name regex signatures for PDB, WDB and CDB type signatures.

  • Build system: Enabled the ability to select a specific Python version. When building, you may use the CMake option -D PYTHON_FIND_VER=<version> to choose a specific Python version. Feature courtesy of Matt Jolly.

  • Added improvements to the ClamOnAcc process log output so that it is easier to diagnose bugs.

  • Windows: Enabled the MSI installer to upgrade between feature versions more easily when ClamAV is installed to a location different from the default (i.e., not C:\Program Files\ClamAV). This means that the MSI installer can find a previous ClamAV 1.0.x installation to upgrade to ClamAV 1.1.0.

  • Sigtool: Added the ability to change the location of the temp directory using the --tempdir option and added the ability to retain the temp files created by Sigtool using the --leave-temps option.

  • Other minor improvements.

Bug fixes

Acknowledgments

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

  • Arjen de Korte
  • Craig Andrews
  • Ged Haywood
  • Matt Jolly
  • Orion Poplawski
  • Nicolas R.
  • Răzvan Cojocaru
  • Red
  • Shawn Iverson
  • Sebastian Andrzej Siewior
  • The OSS-Fuzz project
Posted by at
Labels: , ,
Subscribe to: Posts ( Atom )