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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.21.0701301519590.18631-100000@linuxbox.org>
Date: Tue, 30 Jan 2007 15:23:07 -0600 (CST)
From: Gadi Evron <ge@...uxbox.org>
To: Simple Nomad <thegnome@...c.org>
Cc: Stefano Zanero <s.zanero@...urenetwork.it>, trzindan@...mail.fr,
	bugtraq@...urityfocus.com
Subject: Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include

On Mon, 29 Jan 2007, Simple Nomad wrote:
> 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

They do get posted to bugtraq anyway. :)

> 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.

Indeed, but for those of us trying to make some sense out of all this,
things are somewhat hazy. It is not about working hard or having more
work, it's about seeing if someone has any bright ideas on how to handle
this a bit better.

For example, remot file inclusion attacks are comparable to remote code
execution, testing each and every one of them is not always easy - but
something many of us do anyway.

Maybe it is time for a wiki/bugzilla sort of system to help get things run
more smoothly. Getting it running in this community won't be very easy
though.

You are right on the distribution..

> 
> -SN
>