bugtraq
[Top] [All Lists]

Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include

To: Gadi Evron <ge@linuxbox.org>
Subject: Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include
From: Simple Nomad <thegnome@nmrc.org>
Date: Mon, 29 Jan 2007 16:11:19 -0600
Cc: Stefano Zanero <s.zanero@securenetwork.it>, trzindan@hotmail.fr, bugtraq@securityfocus.com
Delivered-to: sp-com-lists@consult.net
Delivered-to: bugtraq-list@securepoint.com
Delivered-to: mailing list bugtraq@securityfocus.com
Delivered-to: moderator for bugtraq@securityfocus.com
In-reply-to: <Pine.LNX.4.21.0701291259320.14925-100000@linuxbox.org>
List-help: <mailto:bugtraq-help@securityfocus.com>
List-id: <bugtraq.list-id.securityfocus.com>
List-post: <mailto:bugtraq@securityfocus.com>
List-subscribe: <mailto:bugtraq-subscribe@securityfocus.com>
List-unsubscribe: <mailto:bugtraq-unsubscribe@securityfocus.com>
Mailing-list: contact bugtraq-help@securityfocus.com; run by ezmlm
Organization: NMRC
References: <Pine.LNX.4.21.0701291259320.14925-100000@linuxbox.org>
Reply-to: thegnome@nmrc.org
On Mon, 2007-01-29 at 13:00 -0600, Gadi Evron wrote:
> How can we all automate the testing process for fake vulns in and list
> them as such without overburdening OSVDB, CVE, Milworm and SecuriTeam?

How about letting them get posted to bugtraq as ppl test them out
anyway? Usually the testing reports from various ppl on bugtraq bring up
extra info such as "works on the previous version too" or "if foo=0 is
in the config it doesn't work" etc, otherwise someone will want ALL
versions tested before posting.

Bugtraq is probably about as automated as it gets, unless someone wants
to send all their stuff to iDefense or TippingPoint who probably aren't
going to touch the latest lame xss bug or php app bug.

-SN


<Prev in Thread] Current Thread [Next in Thread>