Re: [Full-disclosure] 0day: PDF pwns Windows

On Sat, Sep 22, 2007 at 10:34:07PM -0700, Crispin Cowan wrote:

A "private 0day exploit" (the case I was concerned with) would be where
someone develops an exploit, but does not deploy or publish it, holding
it in reserve to attack others at the time of their choosing. Presumably
if such a person wanted to keep it for very long, they would have to
base it on a vulnerability that they themselves discovered, and did not

I continue to dismiss the requirement that an 0day be found maliciously
exploiting machines, because that requires inferring intent. IMHO, a POC
exploit first posted to Bugtraq ahead of the patch counts as an 0day
exploit, unless it has been so thoroughly obfuscated that the "proof"
part of "proof of concept" is itself BS.

In the case of that "private zero day exploit", then, nobody will ever
know about it except the person that has it waiting in reserve -- and if
someone else discovers and patches the vulnerability before the exploit
is ever used, it never becomes a "public" zero day exploit. In other
words, you can always posit that there's sort of a Heisenbergian state of
potential private zero day exploitedness, but in real, practical terms
there's no zero day anything unless it's public.

The moment you have an opportunity to measure it, the waveforms collapse.

CCD CopyWrite Chad Perrin [ ] interview candidate: "When C++ is your hammer, everything starts
to look like your thumb."

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -