#clamav
#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 Jon Munshaw at 9:06 AM
https://blog.clamav.net/2023/06/shutting-down-old-clamav-bugzilla.html
We are excited to announce the #ClamAV 1.1.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.1.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.1.0.
Please help us validate this release by providing feedback via the ClamAV mailing list or on our Discord.
ClamAV 1.1.0 includes the following improvements and changes:
Major changes
Added the ability to extract images embedded in HTML CSS blocks.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/813
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/852
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/867
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/867
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/852
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/840
Build system: Added CMake option DO_NOT_SET_RPATH to avoid setting RPATH on Unix systems. Feature courtesy of Sebastian Andrzej Siewior.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/815
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/776
Build system: Enabled users to pass in custom Rust compiler flags using the RUSTFLAGS CMake variable. Feature courtesy of Orion Poplawski.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/835
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/855
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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/800
Fixed compile time warnings. Improvement courtesy of Răzvan Cojocaru.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/795
Added a minor optimization when matching domain name regex signatures for PDB, WDB and CDB type signatures.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/837
Build system: Enabled the ability to select a specific Python version. When building, you may use the CMake option -D PYTHON_FIND_VER= to choose a specific Python version. Feature courtesy of Matt Jolly.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/787
Added improvements to the #ClamOnAcc process log output so that it is easier to diagnose bugs.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/822
#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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/872
#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.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/852
Other minor improvements:
Bug fixes
Fixed the broken ExcludePUA / --exclude-pua feature. Fix courtesy of Ged Haywood and Shawn Iverson.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/780
Fixed an issue with integer endianness when parsing Windows executables on big-endian systems. Fix courtesy of Sebastian Andrzej Siewior.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/814
Fixed a possible stack overflow read when parsing WDB signatures. This issue is not a vulnerability.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/807
Fixed a possible index out of bounds when loading CRB signatures. This issue is not a vulnerability.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/810
Fixed a possible use after free when reading logical signatures. This issue is not a vulnerability.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/811
Fixed a possible heap overflow read when reading PDB signatures. This issue is not a vulnerability.
GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/812
Acknowledgments:
Special thanks to the following people for code contributions and bug reports:
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 Micah Snyder at 1:04 PM
#Labels: 1.1.0, #Release_Candidate
As for the other OS, the culprit was clamav. Fortunately, they also provide clamav-lts, which doesn't need Rust to build, so I'm changing over to that.
And I've been messing around with SMT settings in my BIOS, thinking that was to blame. (I had it disabled on my last MB but it was enabled here so I disabled it for comparison. It made my CPU load look half as big, but of course that was just because I had twice as many virtual cores, so the monitor thought I was using less of the imagined double capacity!)
I have just discovered what a threat to Free software Rust is. It makes systemd look trivial.
I have come across its tentacles on another OS, where I have an automated build program which can build 144/145 packages in under half an hour, but one of them is written in Rust, so Rust must be built first, and rust takes over three hours. This will make maintenance of repos unmanageable if programs like that are allowed into the ecosystem. Free Software builders just won't be able to cope.
Clamav is the latest culprit. I have that on my mail servers to provide protection to my Windows-using clients, but I need to find an alternative fast now it's written in Rust.
What I like most about #clamav: you can create your own virus signatures.
Show me another virus scanner that supports that.
#Reminder: #ClamAV 0.102, 0.101 End of Life is Jan 3, 2022
As a reminder, the ClamAV 0.102 and 0.101 releases will reach its end of life (EOL) in less than one month's time on Jan. 3, 2022. After this date, ClamAV 0.102, and 0.101 and all patch versions will be blocked from downloading new signatures from database.clamav.net.
For information about the EOL policy, visit the ClamAV online documentation.
Posted by Micah Snyder at 4:02 PM
Labels: end-of-life
clamav-announce mailing list
clamav-announce@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-announce
#ClamAV 0.104.1 Free #Antivirus Package Updating - LinuxStoney ⚓ https://linuxstoney.com/clamav-0-104-1-free-antivirus-package-updating/
#ClamAV 0.103.4 and 0.104.1 patch releases
ClamAV 0.103.4 LTS and 0.104.1 patch versions are out now. Both of these can be found on clamav.net/downloads, with 0.104.1 as the main release and 0.103.4 under "Previous Stable Releases."
0.103.4
ClamAV 0.103.4 is a critical patch release with the following fixes:
FreshClam:
Add a 24-hour cool-down for FreshClam clients that have received an HTTP 403 (Forbidden) response from the CDN. This is to reduce the volume of 403-response data served to blocked FreshClam clients that are configured with a tight update-loop.
Fixed a bug where FreshClam treats an empty CDIFF as an incremental update failure instead of as an intentional request to download the whole CVD.
ClamDScan: Fix a scan error when broken symlinks are encountered on macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks" options disabled.
Overhauled the scan recursion / nested archive extraction logic and added new limits on embedded file-type recognition performed during the "raw" scan of each file. This limits embedded file-type misidentification and prevents detecting embedded file content that is found/extracted and scanned at other layers in the scanning process.
Fix an issue with the FMap module that failed to read from some nested files.
Fixed an issue where failing to load some rules from a Yara file containing multiple rules may cause a crash.
Fixed assorted compiler warnings.
Fixed assorted Coverity static code analysis issues.
Scan limits:
Added virus-name suffixes to the alerts that trigger when a scan limit has been exceeded. Rather than simply Heuristics.Limits.Exceeded, you may now see limit-specific virus-names, to include:
Heuristics.Limits.Exceeded.MaxFileSize
Heuristics.Limits.Exceeded.MaxScanSize
Heuristics.Limits.Exceeded.MaxFiles
Heuristics.Limits.Exceeded.MaxRecursion
Heuristics.Limits.Exceeded.MaxScanTime
Renamed the Heuristics.Email.ExceedsMax.* alerts to align with the other limit alerts names. These alerts include:
Heuristics.Limits.Exceeded.EmailLineFoldcnt
Heuristics.Limits.Exceeded.EmailHeaderBytes
Heuristics.Limits.Exceeded.EmailHeaders
Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
Heuristics.Limits.Exceeded.EmailMIMEArguments
Fixed an issue where the Email-related scan limits would alert even when the "AlertExceedsMax" (--alert-exceeds-max) scan option is not enabled.
Fixes an issue in the Zip parser where exceeding the "MaxFiles" limit or the "MaxFileSize" limit would abort the scan but would fail to alert. The Zip scan limit issues were independently identified and reported by Aaron Leliaert and Max Allan.
Fixed a leak in the Email parser when using the --gen-json scan option.
Fixed an issue where a failure to record metadata in the Email parser when using the --gen-json scan option could cause the Email parser to abort the scan early and fail to extract and scan additional content.
Fixed a file name memory leak in the Zip parser.
Fixed an issue where certain signature patterns may cause a crash or cause unintended matches on some systems when converting characters to uppercase if a UTF-8 unicode single-byte grapheme becomes a multi-byte grapheme. Patch courtesy of Andrea De Pasquale.
Other fixes backported from 0.104.0:
Fixed a crash in programs that use libclamav when the programs don't set a callback for the "virus found" event. Patch courtesy of Markus Strehle.
Added checks to the the SIS archive parser to prevent an SIS file entry from pointing to the archive, which would result in a loop. This was not an actual infinite loop, as ClamAV's scan recursion limit limits the depth of nested archive extraction.
ClamOnAcc: Fixed a socket file descriptor leak that could result in a crash when all available file descriptors are exhausted.
FreshClam: Fixed an issue where FreshClam would download a CVD repeatedly if a zero-byte CDIFF is downloaded or if the incremental update failed and if the CVD downloaded after that is older than advertised. Patch courtesy of Andrew Williams.
ClamDScan:
Fixed a memory leak of the scan target filename when using the --fdpass or --stream options.
Fixed an issue where ClamDScan would fail to scan any file after excluding a file with the "ExcludePath" option when using when using the --multiscan (-m) option along with either --fdpass or --stream. Also fixed a memory leak of the accidentally-excluded paths in this case.
Fixed a single file path memory leak when using --fdpass.
Fixed an issue where the "ExcludePath" regex may fail to exclude absolute paths when the scan is invoked with a relative path.
Special thanks to the following for code contributions and bug reports:
Aaron Leliaert
Andrea De Pasquale
Andrew Williams
Markus Strehle
Max Allan
0.104.1
ClamAV 0.104.1 is a critical patch release with the following fixes:
FreshClam:
Add a 24-hour cool-down for FreshClam clients that have received an HTTP 403 (Forbidden) response from the CDN. This is to reduce the volume of 403-response data served to blocked FreshClam clients that are configured with a tight update-loop.
Fixed a bug where FreshClam treats an empty CDIFF as an incremental update failure instead of as an intentional request to download the whole CVD.
ClamDScan: Fix a scan error when broken symlinks are encountered on macOS with "FollowDirectorySymlinks" and "FollowFileSymlinks" options disabled.
Overhauled the scan recursion / nested archive extraction logic and added new limits on embedded file-type recognition performed during the "raw" scan of each file. This limits embedded file-type misidentification and prevents detecting embedded file content that is found/extracted and scanned at other layers in the scanning process.
Fix an issue with the FMap module that failed to read from some nested files.
Fixed an issue where failing to load some rules from a Yara file containing multiple rules may cause a crash.
Fixed assorted compiler warnings.
Fixed assorted Coverity static code analysis issues.
Scan limits:
Added virus-name suffixes to the alerts that trigger when a scan limit has been exceeded. Rather than simply Heuristics.Limits.Exceeded, you may now see limit-specific virus-names, to include:
Heuristics.Limits.Exceeded.MaxFileSize
Heuristics.Limits.Exceeded.MaxScanSize
Heuristics.Limits.Exceeded.MaxFiles
Heuristics.Limits.Exceeded.MaxRecursion
Heuristics.Limits.Exceeded.MaxScanTime
Renamed the Heuristics.Email.ExceedsMax.* alerts to align with the other limit alerts names. These alerts include:
Heuristics.Limits.Exceeded.EmailLineFoldcnt
Heuristics.Limits.Exceeded.EmailHeaderBytes
Heuristics.Limits.Exceeded.EmailHeaders
Heuristics.Limits.Exceeded.EmailMIMEPartsPerMessage
Heuristics.Limits.Exceeded.EmailMIMEArguments
Fixed an issue where the Email-related scan limits would alert even when the "AlertExceedsMax" (--alert-exceeds-max) scan option is not enabled.
Fixes an issue in the Zip parser where exceeding the "MaxFiles" limit or the "MaxFileSize" limit would abort the scan but would fail to alert. The Zip scan limit issues were independently identified and reported by Aaron Leliaert and Max Allan.
Fixed a leak in the Email parser when using the --gen-json scan option.
Fixed an issue where a failure to record metadata in the Email parser when using the --gen-json scan option could cause the Email parser to abort the scan early and fail to extract and scan additional content.
Fixed a file name memory leak in the Zip parser.
Fixed an issue where certain signature patterns may cause a crash or cause unintended matches on some systems when converting characters to uppercase if a UTF-8 unicode single-byte grapheme becomes a multi-byte grapheme. Patch courtesy of Andrea De Pasquale.
CMake:
Fix a packaging issue with the Windows *.msi installer so that it will include all of the required files.
Add support for developer code-signing on macOS during the build.
Fix an issue finding and linking with the tinfo library on systems where tinfo is separate from ncurses. Patch courtesy of Luca Barbato.
Tests: Improved the Freshclam incremental update tests to verify correct behavior when a zero-byte CDIFF is downloaded and the CVD served to FreshClam is older than advertised.
Docker: Remove the freshclam.dat file when building the Docker image with the databases-included so FreshClam agents running in the container will have a unique ID in the HTTP User-Agent.
Special thanks to the following for code contributions and bug reports:
Aaron Leliaert
Andrea De Pasquale
Luca Barbato
Max Allan
https://blog.clamav.net/2021/11/clamav-01034-and-01041-patch-releases.html
I have an email where clamdcan complains
Sanesecurity.Jurlbl.0c9ed5.UNOFFICIAL FOUND
It is 100% a false positive.
The signature comes from
root@mx3:~# fgrep Sanesecurity.Jurlbl.0c9ed5 /var/lib/clamav-unofficial-sigs/dbs-ss/jurlbl.ndb
Sanesecurity.Jurlbl.0c9ed5:4:*:(2e|2f|40|20|3c|5f)6e65746d656469612e67726f7570(27|22|20|2f|3d|5f|3e|0a|0d|3f|3c|25|23)
root@mx3:~#
Any ideas how to disable that particular rule?
I know how to mark false positives, but only for attachments, not for entire mails like in my case. Also, I cannot just edit the pattern file, since it is cryptographically signed.