Bug 1165527

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1138101,1165527

# Description of your update
notes=Security fix for CVE-2013-6497

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1138101,1165527

*** Bug 1165587 has been marked as a duplicate of this bug. ***

clamav-0.98.5-1.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/clamav-0.98.5-1.el7

clamav-0.98.5-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/clamav-0.98.5-1.el6

clamav-0.98.5-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/clamav-0.98.5-1.el5

You may want to consider applying patch http://ix.io/ffp (published by Shawn Webb (lattera) of the core clamav development team) or waiting a while until the dust settles. http://lurker.clamav.net/message/20141119.111329.e9922b51.en.html is related.

I specifically asked lattera what he recommends doing in this situation re packagers. He said applying the patch would be ideal.

0.98.6, which contains a fix for this problem and also some other late-breaking bug fixes, might be released "Monday of next week at the very latest".

I can not really see how the Fedora/EPEL packages would be really affected
for regular users (or am I overlooking something?).

Sorry, this may have been a false alarm. I based my comments on the experiences of one other rpm-based packager, who encountered problems when upgrading from 0.98.4 to 0.98.5. Specifically clamd failed during service restart, and clamd did not start at server bootup. Applying the patch helped him, so I figured it might also be needed for EPEL.

I did quite a lot of testing on CentOS6, but I was unable to reproduce that problem. If there is a problem, it might affect EPEL7 because it is packaged differently. There's a separate clamav-lib in EPEL7 (and Fedora), but not in EPEL5/6.

I'll do more testing in CentOS7 tomorrow, it's middle of the night in my timezone now.

Sleep is for the weak.. I ended up testing the EPEL7 version a bit as well, and it did survive "systemctl restart clamd@name" just fine. I guess that's good.

Package clamav-0.98.5-1.el5:
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing clamav-0.98.5-1.el5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4166/clamav-0.98.5-1.el5
then log in and leave karma (feedback).

clamav-0.98.5-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

clamav-0.98.5-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

clamav-0.98.5-1.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.