Wednesday, February 7, 2024

The ClamAV 1.3.0 feature release is now stable!

Today, we are also publishing the 1.2.2 and 1.0.5 security patch versions.

ClamAV 1.1 is past EOL for security fixes and will not receive an update. Switch to the 1.0 LTS, 1.2, or 1.3 versions for continued support.

The release files are available for download on the ClamAV downloads page, on the Github Release page, and through Docker Hub*:
*The Docker images are built on release day and may not be available until later in the day.


Continue reading to learn what changed in each version.


1.3.0

ClamAV 1.3.0 includes the following improvements and changes:

Major changes

  • Added support for extracting and scanning attachments found in Microsoft OneNote section files. OneNote parsing will be enabled by default, but may be optionally disabled using one of the following options:
    a. The clamscan command line option: --scan-onenote=no,
    b. The clamd.conf config option: ScanOneNote no,
    c. The libclamav scan option options.parse &= ~CL_SCAN_PARSE_ONENOTE;,
    d. A signature change to the daily.cfg dynamic configuration (DCONF).

Other improvements

  • Fixed issue when building ClamAV on the Haiku (BeOS-like) operating system. Patch courtesy of Luca D'Amico

  • ClamD: When starting, ClamD will now check if the directory specified by TemporaryDirectory in clamd.conf exists. If it doesn't, ClamD will print an error message and will exit with exit code 1. Patch courtesy of Andrew Kiggins.

  • CMake: If configured to build static libraries, CMake will now also install the libclamav_rust, libclammspack, libclamunrar_iface, and libclamunrar static libraries required by libclamav.

    Note: These libraries are all linked into the clamscan, clamd, sigtool, and freshclam programs, which is why they did not need to be installed to function. However, these libraries would be required if you wish to build some other program that uses the libclamav static library.

    Patch courtesy of driverxdw.

  • Added file type recognition for compiled Python (`.pyc`) files.

      The file type appears as a string parameter for these callback functions:

      - clcb_pre_cache

      - clcb_pre_scan

      - clcb_file_inspection

      When scanning a `.pyc` file, the `type` parameter will now show

      "CL_TYPE_PYTHON_COMPILED" instead of "CL_TYPE_BINARY_DATA".

  • Assorted minor improvements and typo fixes.

Bug fixes

  • ClamOnAcc: Fixed an infinite loop when a file has been deleted before a scan.
    Patch courtesy of gsuehiro.
  • Fixed a possible crash when processing VBA files on HP-UX/IA 64bit. Patch courtesy of Albert Chin-A-Young.

  • ClamConf: Fixed an issue printing `MaxScanSize` introduced with the change to allow a `MaxScanSize` greater than 4 GB.
    Fix courtesy of teoberi.
  • Fixed an issue building a ClamAV RPM in some configurations.
    The issue was caused by faulty CMake logic that intended to create an empty database directory during the installation.

Acknowledgments

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

  • Albert Chin-A-Young
  • Andrew Kiggins
  • driverxdw
  • gsuehiro
  • Luca D'Amico
  • RainRat
  • teoberi

    1.2.2 and 1.0.5

    ClamAV 1.2.2 and ClamAV 1.0.5 are critical patch versions with the following fixes:

    • CVE-2024-20290: Fixed a possible heap overflow read bug in the OLE2 file parser that could cause a denial-of-service (DoS) condition.

      Thank you to OSS-Fuzz for identifying this issue.

      Affected versions:
      • 1.0.0 through 1.0.4 (LTS)
      • 1.1 (all patch versions)
      • 1.2.0 and 1.2.1
    • CVE-2024-20328: Fixed a possible command injection vulnerability in the "VirusEvent" feature of ClamAV's ClamD service.

      To fix this issue, we disabled the '%f' format string parameter.  ClamD administrators may continue to use the `CLAM_VIRUSEVENT_FILENAME`  environment variable, instead of '%f'. But you should do so only from within  an executable, such as a Python script, and not directly in the clamd.conf "VirusEvent" command.

      Thank you to Amit Schendel for identifying this issue.

      Affected versions:
      • 0.104 (all patch versions)
      • 0.105 (all patch versions)
      • 1.0.0 through 1.0.4 (LTS)
      • 1.1 (all patch versions)
      • 1.2.0 and 1.2.1

    Wednesday, January 24, 2024

    We are excited to announce the ClamAV 1.3.0 release candidate.

    You can 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.3.0-rc2.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 these tags:

    • clamav/clamav:unstable
    • clamav/clamav:unstable_base 
    • clamav/clamav-debian:unstable
    • clamav/clamav-debian:unstable_base 

    This release candidate phase is expected to last two weeks before we publish the stable release. Please take this time to evaluate ClamAV 1.3.0.  

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

    Changes since the first release candidate include:

    • ClamOnAcc: Fixed an infinite loop when a file has been deleted before a scan.
      Patch courtesy of gsuehiro.
    • ClamConf: Fixed an issue printing `MaxScanSize` introduced with the change to allow a `MaxScanSize` greater than 4 GB.
      Fix courtesy of teoberi.
    • Fixed an issue building a ClamAV RPM in some configurations.
      The issue was caused by faulty CMake logic that intended to create an empty database directory during the installation.

    You can find the full list of changes and improvements in the blog post for the first release candidate.

    Monday, January 22, 2024

    We now offer official ClamAV docker images based on `debian:11-slim`.

    In addition to offering an alternative to the original Alpine Linux images, the new images are multi-arch images supporting `linux/amd64`, `linux/arm64`, and `linux/ppc64le`.

    ClamAV's Alpine-based and Debian-based Docker images are now built weekly to pick up security fixes in the base images. 

    Check it out here.

    Friday, December 15, 2023

    The ClamAV 1.3.0 release candidate is now available.

    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.3.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.3.0.  

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

    ClamAV 1.3.0 includes the following improvements and changes:

    Major changes

    • Added support for extracting and scanning attachments found in Microsoft OneNote section files. OneNote parsing will be enabled by default, but may be optionally disabled using one of the following options:
      a. The clamscan command line option: --scan-onenote=no,
      b. The clamd.conf config option: ScanOneNote no,
      c. The libclamav scan option options.parse &= ~CL_SCAN_PARSE_ONENOTE;,
      d. A signature change to the daily.cfg dynamic configuration (DCONF).

    Other improvements

    • Fixed issue when building ClamAV on the Haiku (BeOS-like) operating system. Patch courtesy of Luca D'Amico

    • ClamD: When starting, ClamD will now check if the directory specified by TemporaryDirectory in clamd.conf exists. If it doesn't, ClamD will print an error message and will exit with exit code 1. Patch courtesy of Andrew Kiggins.

    • CMake: If configured to build static libraries, CMake will now also install the libclamav_rust, libclammspack, libclamunrar_iface, and libclamunrar static libraries required by libclamav.

      Note: These libraries are all linked into the clamscan, clamd, sigtool, and freshclam programs, which is why they did not need to be installed to function. However, these libraries would be required if you wish to build some other program that uses the libclamav static library.

      Patch courtesy of driverxdw.

    • Added file type recognition for compiled Python (`.pyc`) files.

        The file type appears as a string parameter for these callback functions:

        - `clcb_pre_cache`

        - `clcb_pre_scan`

        - `clcb_file_inspection`

        When scanning a `.pyc` file, the `type` parameter will now show

        "CL_TYPE_PYTHON_COMPILED" instead of "CL_TYPE_BINARY_DATA".

    • Assorted minor improvements and typo fixes.

    Bug fixes

    Acknowledgments

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

    • Albert Chin-A-Young
    • Andrew Kiggins
    • driverxdw
    • Luca D'Amico
    • RainRat

    Wednesday, October 25, 2023

    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:


    Monday, August 28, 2023

    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: