Re: defining 0day
- From: Chad Perrin <perrin@xxxxxxxxxxxx>
- Date: Wed, 26 Sep 2007 17:10:32 -0600
On Wed, Sep 26, 2007 at 04:25:30PM -0700, Zow Terry Brugger wrote:
As a professional, I would be happy to see terms like '0day' banished
from the lexicon entirely. It's an essentially meaningless -- all
third-party exploits are zero-day to _somebody_ -- term of boast co-
opted from the warez scene, and we can do perfectly well without it.
I'd accept that. Can we agree on a term that means: "Right now you're
learning about a vulnerability for which there is a working exploit, and no
way to protect yourself short of impacting the availability of your systems
by unplugging them or disabling the affected service."?
I'd propose "unpatched vulnerability with known working exploit", but it's
kind of verbose, and I don't think some of the kids joining our ranks can
string that many complete words together anymore (too much texting).
UV:WE
Unpatched Vulnerability: Working Exploit
. . . or maybe "zero day exploit".
--
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
Brian K. Reid: "In computer science, we stand on each other's feet."
- Follow-Ups:
- RE: defining 0day
- From: Marvin Simkin
- RE: defining 0day
- References:
- Re: 0day: PDF pwns Windows
- From: Gadi Evron
- Re: 0day: PDF pwns Windows
- From: Crispin Cowan
- Re: 0day: PDF pwns Windows
- From: Crispin Cowan
- Re: 0day: PDF pwns Windows
- From: Chad Perrin
- Re: 0day: PDF pwns Windows
- From: Lamont Granquist
- Re: 0day: PDF pwns Windows
- From: Roland Kuhn
- RE: 0day: PDF pwns Windows
- From: Thor (Hammer of God)
- defining 0day
- From: Gadi Evron
- Re: defining 0day
- From: Charles Miller
- Re: defining 0day
- From: Zow
- Re: 0day: PDF pwns Windows
- Prev by Date: [ GLSA 200709-16 ] Lighttpd: Buffer overflow
- Next by Date: [ MDKSA-2007:189 ] - Updated t1lib packages fix vulnerability
- Previous by thread: Re: defining 0day
- Next by thread: RE: defining 0day
- Index(es):
Relevant Pages
|