Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Vuln-Dev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: defining 0day

from [Chad Perrin] Network Security [Permanent Link]
Subject: Re: defining 0day
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."
[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [ GLSA 200709-16 ] Lighttpd: Buffer overflow, Pierre-Yves Rofes
Next by Date:  [SECURITY] [DSA 1378-1] New Linux 2.6.18 packages fix several vulnerabilities, dann frazier
Previous by Thread:  Re: [Full-disclosure] defining 0day, Zow
Next by Thread:  RE: defining 0day, Marvin Simkin
Indexes:  [Date] [Thread] [Top] [All Lists]