Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Bugtraq
[Top] [All Lists]

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

Subject: Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include
Date: Tue, 30 Jan 2007 15:23:07 -0600 (CST)
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


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