Closed GoogleCodeExporter closed 8 years ago
Original comment by tav...@google.com
on 8 Sep 2015 at 10:11
Attachments:
Kaspersky replied and confirmed this issue and believe they can deploy a fix
today (09 Sep).
Original comment by tav...@google.com
on 9 Sep 2015 at 7:01
Original comment by scvi...@google.com
on 10 Sep 2015 at 1:46
Original comment by tav...@google.com
on 22 Sep 2015 at 5:44
Is this POC password protected? Are you going to wait 90 days to release the
POC?
Original comment by athmi...@gmail.com
on 24 Sep 2015 at 9:52
The password is "infected", Kaspersky requested that (presumably to prevent
crashing their mail servers and development machines).
Original comment by tav...@google.com
on 24 Sep 2015 at 10:01
Awesome!! Thank you very much!
Original comment by athmi...@gmail.com
on 24 Sep 2015 at 10:15
Also it looks like Kaspersky is preventing windbg from attaching to its
processes. You output looks like its from windbg. How did you manage to get
around this?
Original comment by athmi...@gmail.com
on 24 Sep 2015 at 10:31
They use a driver to interfere with debugging, but there's an option in the
settings UI called "self defense" that disables it.
Original comment by tav...@google.com
on 24 Sep 2015 at 10:36
great! Thank you so much!
Original comment by athmi...@gmail.com
on 24 Sep 2015 at 10:37
Sorry to bother you so much, but is it possible to obtain the POC before
fuzzing? With the Microsoft office ones, both the fuzzed poc and original
normal were provided. Thank you for your help!
Original comment by athmi...@gmail.com
on 25 Sep 2015 at 5:46
Original comment by haw...@google.com
on 12 Oct 2015 at 6:12
Original issue reported on code.google.com by
tav...@google.com
on 8 Sep 2015 at 10:11