Hello, Thank you..
I agree with you and also aware about it as old vulnerability and to use of latest/patched software. However, my intention was to detect it before it get deliver to user. Especially when other AV could detect it and block it. I will wait for response from clamav team. With Regards Jigar On Sat, Apr 3, 2021, 22:26 G.W. Haywood via clamav-users < clamav-users@lists.clamav.net> wrote: > Hi there, > > On Sat, 3 Apr 2021, Jigar via clamav-users wrote: > > > Any update w.r.t. submitted infected file and signature?. > > This vulnerability was patched by Microsoft more than three years ago. > > For example, see > > https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2017-11882 > > There should be no vulnerable versions of the software running now. > > As this is such an old threat, and mitigated a long time ago, you seem > to me to be more concerned about it than I would expect anyone to be. > > Is there any particular reason for that? > > If you supplied your email address to the ClamAV signature team when > you reported the malware samples you will get an email in due course > if a new signature is developed. OTOH I should not expect them to be > putting this one at the front of their schedule. > > If you are using vulnerable software, patch it. > > -- > > 73, > Ged. > > _______________________________________________ > > clamav-users mailing list > clamav-users@lists.clamav.net > https://lists.clamav.net/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml >
_______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
