Thanks Andrew.
- Alain
On Thu, Dec 12, 2013 at 6:01 PM, Andrew Carter
wrote:
> Hi Douglas,
>
> I have tested the file now and it is testing as clean. Thank you for
> resolving this.
>
> Kind regards,
>
> Andrew
>
>
> On 13/12/13 11:40, Douglas Goddard wrote:
>
>> It was an oversight on our end.
Hi Douglas,
I have tested the file now and it is testing as clean. Thank you for
resolving this.
Kind regards,
Andrew
On 13/12/13 11:40, Douglas Goddard wrote:
It was an oversight on our end. Thank you for being persistent. The
offending bytecode has been dropped and the fixed code has been
It was an oversight on our end. Thank you for being persistent. The
offending bytecode has been dropped and the fixed code has been published.
On Thu, Dec 12, 2013 at 4:22 AM, Al Varnell wrote:
> On Wed, Dec 11, 2013 at 06:56 AM, Douglas Goddard wrote:
> > When was your last signature update? C
On Wed, Dec 11, 2013 at 06:56 AM, Douglas Goddard wrote:
> When was your last signature update? Could you run freshclam and then
> rescan? That version of the bytecode signature has been dropped and should
> no longer be alerting, the current version is BC.Exploit.CVE_2013_3906-3.
> If that version
I too reported the false positive. I supplied the offending file was that
correct?
I have 18 other different files that report the same exploit like so -
559 /root$ freshclam
ClamAV update process started at Thu Dec 12 08:54:47 2013
main.cvd is up to date (version: 55, sigs: 2424225, f-level: 6
