Actually, looks like this was fixed already. The 30s ReceiveTimeout default value was being set in eoan's clamav-freshclam.postinst:
[ -z "$ReceiveTimeout" ] && ReceiveTimeout=30
This was later changed to 0 in the package version 0.102.2+dfsg-1:
clamav (0.102.2+dfsg-1) unstable; urgency=medium
* Import 0.102.2
- CVE-2020-3123 (DoS may occur in the optional DLP feature)
(Closes: 950944).
* Update symbol file.
* Set ReceiveTimeout to 0 which is upstream default.
Which is in Ubuntu Focal. Therefore, this bug is fixed in that upcoming release.
Actually, looks like this was fixed already. The 30s ReceiveTimeout default value was being set in eoan's clamav- freshclam. postinst:
[ -z "$ReceiveTimeout" ] && ReceiveTimeout=30
This was later changed to 0 in the package version 0.102.2+dfsg-1:
clamav (0.102.2+dfsg-1) unstable; urgency=medium
* Import 0.102.2
- CVE-2020-3123 (DoS may occur in the optional DLP feature)
(Closes: 950944).
* Update symbol file.
* Set ReceiveTimeout to 0 which is upstream default.
Which is in Ubuntu Focal. Therefore, this bug is fixed in that upcoming release.