That’s almost impossible in that clamav only reports infected files, it doesn’t
modify them and doesn’t delete them by default.
I have crashed a system into an unbootable state by fuzzing clamav which
resulted in a filled hard drive and no inodes left.
Sent from my iPhone
> On Jul 17, 2019,
After scanning home folder with ClamAv (up-to-date definitions) in Fedora
30, O.S. crashed and became unbootable.
___
clamav-devel mailing list
clamav-devel@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-devel
Please submit your
Thanks for tracking this down Mark. Sorry we didn’t respond earlier. It has
been a crazy couple weeks over here. Will take a look at the issue and your
patches soon.
-Micah
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
From: clamav-devel on behalf of Mark
Allan
Reply-To:
OK, so tracking this one down took longer than I like to admit!
The issue seems to have crept in with commits 3e42216cc and 28afc94c3 back in
April/May 2017.
Attached are patches for devel/HEAD as well as the stable 0.101.2
Tests show that the issue is fixed and doesn't appear to introduce
