[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption

To: <full-disclosure@lists.netsys.com>
Subject: RE: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
From: "Richard M. Smith" <rms@computerbytesman.com>
Date: Tue, 10 Feb 2004 21:40:32 -0500

Hi Marc, 

   >>> Date Reported: July 25, 2003

Given that it took Microsoft almost 6 months to fix this problem, I'm
wondering how many other Eeye security holes are in the queue that Microsoft
is currently working on.  Enquiring minds would like to know! ;-)

Richard

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

Follow-Ups:
- RE: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
  - From: Byron Copeland <nodialtone@comcast.net>
- Re: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
  - From: Damian Gerow <damian@sentex.net>
- RE: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
  - From: "Les Ault" <aultl@comcast.net>

References:
- [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
  - From: "Marc Maiffret" <mmaiffret@eeye.com>

Prev by Date: [Full-Disclosure] RE: Another Low Blow From Microsoft: MBSA Failure!
Next by Date: Re: [Full-Disclosure] anti-adware and false positives (was: Virusinfect on single user)
Previous by thread: Re: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
Next by thread: RE: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Length Overflow Heap Corruption
Index(es):
- Date
- Thread