Changelog for clamav-devel-0.103.11-3.2.x86_64.rpm :

* Mon Feb 26 2024 Dominique Leuenberger - Use %patch -P N instead of deprecated %patchN.
* Wed Oct 25 2023 Arjen de Korte - Update to 0.103.11
* Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
* Windows: libjson-c 0.17 compatibility fix. with ssize_t type definition.
* Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.- Update to 0.103.10
* Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.10. (bsc#1216625, CVE-2023-40477)
* Fri Aug 18 2023 Reinhard Max - Renew clamav.keyring .
* Wed Aug 16 2023 Arjen de Korte - Update to 0.103.9
* 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. (boo#1214342)
* Fixed compiler warnings that may turn into errors in Clang 16.
* Wed Feb 15 2023 Arjen de Korte - Update to 0.103.8
* CVE-2023-20032: Fixed a possible remote code execution vulnerability in the HFS+ file parser. Issue affects versions 1.0.0 and earlier, 0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208363)
* CVE-2023-20052: Fixed a possible remote information leak vulnerability in the DMG file parser. Issue affects versions 1.0.0 and earlier, 0.105.1 and earlier, and 0.103.7 and earlier. (bsc#1208365)
* Update vendored libmspack library to version 0.11alpha.- Package huge .html documentation in a separate subpackage.
* Fri Aug 05 2022 ecsos - Update to 0.103.7 - Zip parser: tolerate 2-byte overlap in file entries - Fix bug with logical signature Intermediates feature - Update to UnRAR v6.1.7 - Patch UnRAR: allow skipping files in solid archives - Patch UnRAR: limit dict winsize to 1GB
* Thu May 05 2022 Arjen de Korte - Update to 0.103.6
* CVE-2022-20770: Fixed a possible infinite loop vulnerability in the CHM file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior versions. (boo#1199242)
* CVE-2022-20796: Fixed a possible NULL-pointer dereference crash in the scan verdict cache check. Issue affects versions 0.103.4, 0.103.5, 0.104.1, and 0.104.2. (boo#1199246)
* CVE-2022-20771: Fixed a possible infinite loop vulnerability in the TIFF file parser. Issue affects versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior versions. The issue only occurs if the \"--alert-broken-media\" ClamScan option is enabled. For ClamD, the affected option is \"AlertBrokenMedia yes\", and for libclamav it is the \"CL_SCAN_HEURISTIC_BROKEN_MEDIA\" scan option. (boo#1199244)
* CVE-2022-20785: Fixed a possible memory leak in the HTML file parser / Javascript normalizer. Issue affects versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior versions. (boo#1199245)
* CVE-2022-20792: Fixed a possible multi-byte heap buffer overflow write vulnerability in the signature database load module. The fix was to update the vendored regex library to the latest version. Issue affects versions 0.104.0 through 0.104.2 and LTS version 0.103.5 and prior versions. (boo#1199274)
* ClamOnAcc: Fixed a number of assorted stability issues and added niceties for debugging ClamOnAcc.
* Fixed an issue causing byte-compare subsignatures to cause an alert when they match even if other conditions of the given logical signatures were not met.
* Fix memleak when using multiple byte-compare subsignatures. This fix was backported from 0.104.0.
* Assorted bug fixes and improvements.- Remove upstreamed clamav-ck_assert_msg.patch
* Tue Apr 12 2022 Marcus Meissner - https source urls
* Wed Jan 12 2022 Arjen de Korte - Update to 0.103.5
* CVE-2022-20698: Fix for invalid pointer read that may cause a crash. This issue affects 0.104.1, 0.103.4 and prior when ClamAV is compiled with libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option (the clamscan --gen-json option) is enabled.
* Fixed ability to disable the file size limit with libclamav C API, like this: cl_engine_set_num(engine, CL_ENGINE_MAX_FILESIZE, 0); This issue didn\'t affect ClamD or ClamScan which also can disable the limit by setting it to zero using MaxFileSize 0 in clamd.conf for ClamD, or clamscan --max-filesize=0 for ClamScan. Note: Internally, the max file size is still set to 2 GiB. Disabling the limit for a scan will fall back on the internal 2 GiB limitation.
* Increased the maximum line length for ClamAV config files from 512 bytes to 1,024 bytes to allow for longer config option strings.
* SigTool: Fix insufficient buffer size for --list-sigs that caused a failure when listing a database containing one or more very long signatures. This fix was backported from 0.104.
* Wed Nov 03 2021 Arjen de Korte - bsc#1192346: Update to 0.103.4
* 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.
* Wed Jun 30 2021 Marcus Meissner - clamav-document-maxsize.patch: in the \"clamscan\" and \"clamdscan\" manpages, document that files over a certain size by default will silently not be scanned and how this can be adjusted (bsc#1187509)
* Mon Jun 21 2021 Arjen de Korte - bsc#1188284: Update to 0.103.3
* Fixed a scan performance issue when ENGINE_OPTIONS_FORCE_TO_DISK is enabled. This issue did not impacted most users but for those affected it caused every scanned file to be copied to the temp directory before the scan.
* Fix ClamDScan crashes when using the --fdpass --multiscan command-line options in combination with the ClamD ExcludePath config file options.
* Fixed an issue where the mirrors.dat file is owned by root when starting as root (or with sudo) and using daemon-mode. File ownership will be set to the DatabaseOwner just before FreshClam switches to run as that user.
* Renamed the mirrors.dat file to freshclam.dat.
* Disabled the HTTPUserAgent config option if the DatabaseMirror uses clamav.net. This will prevent users from being inadvertently blocked and will ensure that we can keep better metrics on which ClamAV versions are being used.
* Moved the detection for Heuristics.PNG.CVE-2010-1205 behind the ClamScan --alert-broken-media option (ClamD AlertBrokenMedia yes) option. This type of PNG issue appears to be common enough to be an annoyance, and the CVE is old enough that no one should be vulnerable at this point.
* Fix ClamSubmit failures after changes to Cloudflare \"__cfduid\" cookies. See: https://blog.cloudflare.com/deprecating-cfduid-cookie/
* Fri Apr 09 2021 Reinhard Max - Use a split-provides for clamav-milter instead of recommending it.
* Wed Apr 07 2021 Arjen de Korte - Update to 0.103.2
* CVE-2021-1252, bsc#1184532: Fix for Excel XLM parser infinite loop. Affects 0.103.0 and 0.103.1 only.
* CVE-2021-1404, bsc#1184533: Fix for PDF parser buffer over-read; possible crash. Affects 0.103.0 and 0.103.1 only.
* CVE-2021-1405, bsc#1184534: Fix for mail parser NULL-dereference crash. Affects 0.103.1 and prior.
* Fix possible memory leak in PNG parser.
* Fix ClamOnAcc scan on file-creation race condition so files are scanned after their contents are written.
* FreshClam: Deprecate the SafeBrowsing config option. The SafeBrowsing option will no longer do anything.
* For more details, see our blog post from last year about the future of the ClamAV Safe Browsing database.
* FreshClam: Improved HTTP 304, 403, & 429 handling.
* FreshClam: Added back the mirrors.dat file to the database directory.
* FreshClam will now exit with a failure in daemon mode if an HTTP 403 (Forbidden) was received, because retrying later won\'t help any. The FreshClam user will have to take actions to get unblocked.
* Fix the FreshClam mirror-sync issue where a downloaded database is \"older than the version advertised.\"
* bsc#1181256: Fix errors when scanning files > 4G- Update package signing key (from https://www.clamav.net/downloads) % clamav.keyring
* Thu Feb 25 2021 Arjen de Korte - Package clamav-milter in a subpackage- Remove virus signatures upon uninstall- Check for database existence before starting clamd- Restart clamd when it exits
* Tue Feb 09 2021 Arjen de Korte - Don\'t daemonize freshclam, but use a systemd timer instead to trigger updates + timer.freshclam % service.freshclam % clamav-conf.patch- Remove obsolete patch (replaced by SOURCE_DATE_EPOCH) - clamav-disable-timestamps.patch- Fix unit test + clamav-ck_assert_msg.patch- Cleanup spec
* use pkgconfig() to resolve BuildRequires where upstream uses it
* rework creating vscan user (new system-user in Tumbleweed)
* remove obsolete configure option --disable-zlib-vcheck
* Sat Feb 06 2021 Arjen de Korte - Update to 0.103.1
* Added a new scan option to alert on broken media (graphics) file formats. This feature mitigates the risk of malformed media files intended to exploit vulnerabilities in other software. At present media validation exists for JPEG, TIFF, PNG, and GIF files. To enable this feature, set AlertBrokenMedia yes in clamd.conf, or use the --alert-broken-media option when using clamscan. These options are disabled by default in this patch release, but may be enabled in a subsequent release. Application developers may enable this scan option by enabling CL_SCAN_HEURISTIC_BROKEN_MEDIA for the heuristic scan option bit field.
* Added CL_TYPE_TIFF, CL_TYPE_JPEG types to match GIF, PNG typing behavior. BMP and JPEG 2000 files will continue to detect as CL_TYPE_GRAPHICS because ClamAV does not yet have BMP or JPEG 2000 format checking capabilities.
* Fixed PNG parser logic bugs that caused an excess of parsing errors and fixed a stack exhaustion issue affecting some systems when scanning PNG files. PNG file type detection was disabled via signature database update for ClamAV version 0.103.0 to mitigate the effects from these bugs.
* Fixed an issue where PNG and GIF files no longer work with Target:5 graphics signatures if detected as CL_TYPE_PNG/GIF rather than as CL_TYPE_GRAPHICS. Target types now support up to 10 possible file types to make way for additional graphics types in future releases.
* Fixed clamonacc\'s --fdpass option. - Interprocess file descriptor passing for clamonacc was broken since version 0.102.0 due to a bug introduced by the switch to curl for communicating with clamd. On Linux, passing file descriptors from one process to another is handled by the kernel, so we reverted clamonacc to use standard system calls for socket communication when fd passing is enabled.
* Fixed a clamonacc stack corruption issue on some systems when using an older version of libcurl.
* Allow clamscan and clamdscan scans to proceed even if the realpath lookup failed. This alleviates an issue on Windows scanning files hosted on file- systems that do not support the GetMappedFileNameW() API such as on ImDisk RAM-disks.
* Fixed freshclam --on-update-execute=EXIT_1 temporary directory cleanup issue.
* clamd\'s log output and VirusEvent now provide the scan target\'s file path instead of a file descriptor. The clamd socket API for submitting a scan by FD-passing doesn\'t include a file path, this feature works by looking up the file path by file descriptor. This feature works on Mac and Linux but is not yet implemented for other UNIX operating systems. FD-passing is not available for Windows.
* Fixed an issue where freshclam database validation didn\'t work correctly when run in daemon mode on Linux/Unix.