Re: [Full-disclosure] [fuzzing] NOT a 0day! Re: OWASP Fuzzing page

2006-12-21 Thread Jerome Athias
Gadi Evron a écrit :
 On Tue, 12 Dec 2006, Joxean Koret wrote:
   
 Wow! That's fun! The so called Word 0 day flaw also affects
 OpenOffice.org! At least, 1.1.3. And, oh! Abiword does something cool
 with the file:
 

 This is NOT a 0day. It is a disclosed vulnerability in full-disclosure
 mode, on a mailing list (fuzzing mailing list).

 I am not sure why I got this 10 times now, I thought the days of these
 bounces were over. But I am tired of seeing every full-disclosure
 vulnerability called a 0day anymore.

 A 0day, whatever definition you use, is used in the wild before people are
 aware of it.
It makes sense and I totally agree with you.
But the fact is that the things change (and not allways in the right 
direction :-()... due to the society, money, research of popularity...
Please remember us also the sense of the word hacker for instance, 
since nowadays it's often use to speak about bad guy/blackhat/pirate - 
i hope you'll agree that it's not the (our) sense

/JA

___
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


Re: [Full-disclosure] [fuzzing] NOT a 0day! Re: OWASP Fuzzing page

2006-12-14 Thread Gadi Evron
On Thu, 14 Dec 2006, Jerome Athias wrote:
 Gadi Evron a écrit :
  On Tue, 12 Dec 2006, Joxean Koret wrote:

  Wow! That's fun! The so called Word 0 day flaw also affects
  OpenOffice.org! At least, 1.1.3. And, oh! Abiword does something cool
  with the file:
  
 
  This is NOT a 0day. It is a disclosed vulnerability in full-disclosure
  mode, on a mailing list (fuzzing mailing list).
 
  I am not sure why I got this 10 times now, I thought the days of these
  bounces were over. But I am tired of seeing every full-disclosure
  vulnerability called a 0day anymore.
 
  A 0day, whatever definition you use, is used in the wild before people are
  aware of it.
 It makes sense and I totally agree with you.
 But the fact is that the things change (and not allways in the right 
 direction :-()... due to the society, money, research of popularity...
 Please remember us also the sense of the word hacker for instance, 
 since nowadays it's often use to speak about bad guy/blackhat/pirate - 
 i hope you'll agree that it's not the (our) sense

This battle is not lost. If we call it the right name and talk to the
press using the right terms, it is not lost yet. Maybe it should be, but
it is really confusing when it gets to the professional community.

 
 /JA
 

___
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


Re: [Full-disclosure] [fuzzing] NOT a 0day! Re: OWASP Fuzzing page

2006-12-14 Thread Juha-Matti Laurio
After the public release we have to accept the fact that the PoC will be 
possibly accessible outside of exploit sites too.
The overall risk of the issue is increasing.
To confirm the existence of PoC it was listed in several references like
http://www.securityfocus.com/bid/21589/exploit
etc.

The metadata information of 12122006-djtest.doc states the following:

Created: 16th Aug 2006
Author: sarahbl

- Juha-Matti


Gadi Evron [EMAIL PROTECTED] wrote: 
 On Tue, 12 Dec 2006, Joxean Koret wrote:
  
  Wow! That's fun! The so called Word 0 day flaw also affects
  OpenOffice.org! At least, 1.1.3. And, oh! Abiword does something cool
  with the file:
 
 This is NOT a 0day. It is a disclosed vulnerability in full-disclosure
 mode, on a mailing list (fuzzing mailing list).
 
 I am not sure why I got this 10 times now, I thought the days of these
 bounces were over. But I am tired of seeing every full-disclosure
 vulnerability called a 0day anymore.
 
 A 0day, whatever definition you use, is used in the wild before people are
 aware of it.
 
 
  
  [EMAIL PROTECTED] $ abiword 12122006-djtest.doc
  
  ** (AbiWord-2.2:24313): WARNING **: Invalid seek
  
  ** (AbiWord-2.2:24313): WARNING **: Invalid seek
  
  ** (AbiWord-2.2:24313): WARNING **: Invalid seek
  
  ** (AbiWord-2.2:24313): WARNING **: Invalid seek
  [EMAIL PROTECTED] $ ooffice 12122006-djtest.doc
  OpenOffice.org lockfile found (/home/joxean/.openoffice/1.1.3/.lock)
  Using existing OpenOffice.org
  Application Errorsh: line 1: crash_report: command not found
  Application Error
  
  Fatal exception: Signal 6

--clip--

___
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


Re: [Full-disclosure] [fuzzing] NOT a 0day! Re: OWASP Fuzzing page

2006-12-14 Thread Gadi Evron
On Thu, 14 Dec 2006, Juha-Matti Laurio wrote:
 After the public release we have to accept the fact that the PoC will be 
 possibly accessible outside of exploit sites too.
 The overall risk of the issue is increasing.
 To confirm the existence of PoC it was listed in several references like
 http://www.securityfocus.com/bid/21589/exploit
 etc.
 
 The metadata information of 12122006-djtest.doc states the following:
 
 Created: 16th Aug 2006
 Author: sarahbl

Not a 0day.

 
 - Juha-Matti
 
 
 Gadi Evron [EMAIL PROTECTED] wrote: 
  On Tue, 12 Dec 2006, Joxean Koret wrote:
   
   Wow! That's fun! The so called Word 0 day flaw also affects
   OpenOffice.org! At least, 1.1.3. And, oh! Abiword does something cool
   with the file:
  
  This is NOT a 0day. It is a disclosed vulnerability in full-disclosure
  mode, on a mailing list (fuzzing mailing list).
  
  I am not sure why I got this 10 times now, I thought the days of these
  bounces were over. But I am tired of seeing every full-disclosure
  vulnerability called a 0day anymore.
  
  A 0day, whatever definition you use, is used in the wild before people are
  aware of it.
  
  
   
   [EMAIL PROTECTED] $ abiword 12122006-djtest.doc
   
   ** (AbiWord-2.2:24313): WARNING **: Invalid seek
   
   ** (AbiWord-2.2:24313): WARNING **: Invalid seek
   
   ** (AbiWord-2.2:24313): WARNING **: Invalid seek
   
   ** (AbiWord-2.2:24313): WARNING **: Invalid seek
   [EMAIL PROTECTED] $ ooffice 12122006-djtest.doc
   OpenOffice.org lockfile found (/home/joxean/.openoffice/1.1.3/.lock)
   Using existing OpenOffice.org
   Application Errorsh: line 1: crash_report: command not found
   Application Error
   
   Fatal exception: Signal 6
 
 --clip--
 

___
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/