Clamd can't start if FailIfCvdOlderThan is defined and a white list is used

[jmlrt]

Describe the bug

clamd fail to start when FailIfCvdOlderThan is defined in clamd.conf and a whitelist file is created in /var/lib/clamav.

How to reproduce the problem

$ echo "CVE_2012_0773-2" > /var/lib/clamav/my_whitelist.ign2
$ clamd
LibClamAV Error: cli_cvdverify: Can't read CVD header
LibClamAV Error: cl_cvdgetage: cvdgetfileage() failed for /var/lib/clamav/my_whitelist.ign2
ERROR: Broken or not a CVD file
$ clamconf -n
Checking configuration files in /etc/clamav

Config file: clamd.conf
-----------------------
AlertExceedsMax yes
FailIfCvdOlderThan 10
LocalSocket /home/clamav/clamd.sock
LogClean yes
LogFile  /home/clamav/clamd.log
LogFileMaxSize 0
MaxDirectoryRecursion 100
MaxFileSize 0
MaxFiles 0
MaxScanSize 0
MaxScanTime 0
MaxThreads 6
OnAccessExcludeUID 23
OnAccessIncludePath /clamav/files-to-scan/
OnAccessMaxFileSize 0
OnAccessMaxThreads 6
PidFile /home/clamav/clamd.pid
SelfCheck 72000
User clamav

Config file: freshclam.conf
---------------------------
PidFile = "/run/clamav/freshclam.pid"
DatabaseMirror = "database.clamav.net"

clamav-milter.conf not found

Software settings
-----------------
Version: 1.2.2
Optional features supported: MEMPOOL AUTOIT_EA06 BZIP2 LIBXML2 PCRE2 ICONV JSON

Database information
--------------------
Database directory: /var/lib/clamav
main.cvd: version 62, sigs: 6647427, built on Thu Sep 16 12:32:42 2021
bytecode.cvd: version 334, sigs: 91, built on Wed Feb 22 21:33:21 2023
daily.cvd: version 27181, sigs: 2052851, built on Sat Feb 10 09:34:05 2024
[3rd Party] my_whitelist.ign2: 1 sig
Total number of signatures: 8700370

Platform information
--------------------
uname: Linux 6.6.12-linuxkit #1 SMP Fri Jan 19 08:53:17 UTC 2024 x86_64
OS: Linux, ARCH: x86_64, CPU: x86_64
zlib version: 1.3.1 (1.3.1), compile flags: a9
platform id: 0x0a21c0c008000000000d0201

Build information
-----------------
GNU C: 13.2.1 20231014 (13.2.1)
sizeof(void*) = 8
Engine flevel: 192, dconf: 192

Attachments

If applicable, add screenshots to help explain your problem.

If the issue is reproducible only when scanning a specific file, attach it to the ticket.

[brebell]

Thank you for calling this bug to our attention.