Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Vulnerability Development: Re: [Full-Disclosure] Re: Clarification on Xitami DoS

Re: [Full-Disclosure] Re: Clarification on Xitami DoS

From: Steven M. Christey <coley_at_linus.mitre.org>
Date: Mon, 5 Aug 2002 12:46:13 -0400 (EDT)

Muhammad Faisal Rauf Danka <mfrd_at_attitudex.com> asked:

>What is vendor's status regarding this issue?

to which "Matthew Murphy" <mattmurphy_at_kc.rr.com> replied:

>I've e-mailed the vendor, but have received no response *at all*.

This thread is a good demonstration for why vendors need to be
responsive to incoming vulnerability reports. Without a response from
the vendor, we've now got a number of posts in which people have spent
extra time to (a) try to figure out the underlying cause of the issue,
(b) try to duplicate the issue, and (c) try to come up with a
resolution in the absence of vendor guidance and/or a patch. Vendors
often know the answers to these questions.

Greater overall responsiveness by vendors is covered heavily by
section 3 of the Responsible Vulnerability Disclosure Process draft
[1]. Better responsiveness from vendors (and better coordination
overall) can reduce much of this guesswork, so that sysadmins and
security researchers can spend their time on more pressing issues.

- Steve

[1] http://www.ietf.org/internet-drafts/draft-christey-wysopal-vuln-disclosure-00.txt
Received on Aug 05 2002

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos