Re: [WEB SECURITY] Jikto in the wild

["pdp (architect)" <pdp.gnucitizen@xxxxxxxxxxxxxx>]

Billy,

I saw Jikto's code probably on the same day when you did your
presentation. The truth is that, although it is possible for someone
to use Jikto to vuln asses a server, at the moment this is very
unlikely. Probably I make too strong statement here but this is what
think. :)

Today, it is a lot easer to scan someone through TOR then using
browser issues. Why? Well, it will take some time for the bad guys to
pick the new ideas and not only that,... but also to create a big
enough infrastructure to support Jikto's mobility.

This is why I believe that Jikto should be made free for everyone to
see. As you mentioned, the code is largely constructed from various
snippets which are available anyway. It took you 24h to assemble the
code... well the bad guys may spend 10 days to do the same but they
will achieve it eventually and I believe that there are already enough
resources out there to simplify the task even more.

So my suggestion is to make it free. I am working myself on something
that may lead to a lot of problems but this is our job after all. We
don't prevent something from happening, we are just messengers. It is
up to the vendors and the community to decide what to do with it.
Although I do consulting for companies and corporations and I making
living out of it, I never sell false ideas such as a service or
product that magically resolves problems. The truth is that if someone
wants to penetrate your organization, they will, and you can do
nothing about it. All we give is a warning, a bit of information that
will make a difference eventually.

That's all I am saying.

On 4/2/07, Billy Hoffman <Billy.Hoffman@xxxxxxxxxxxxxxx> wrote:
> FYI: Jikto's in the wild. You can read about it here:
> http://portal.spidynamics.com/blogs/spilabs/archive/2007/04/02/Jikto-in-the-wild.aspx
>
>
>
> I supposed it was only a matter of time. As the post describes, I took a
> bunch of steps to protect the code during my demo. Even if someone hadn't
> managed to grab a copy, I image a Jikto clone would have come out sometime
> this year. In fact, pdp was so close back in October with his web crawling
> demo. His work heavily influenced Jikto. His solution however used timer and
> iframe remoting and as I've said before
> (http://www.gnucitizen.org/blog/javascript-remoting-dangers)
> XmlHttpRequest is way faster than iframes.
>
>
>
> Using pdp's idea, all I had to do for Jikto was write ~800 of JavaScript
> functions to handle response parsing, link scrapping, URL resolution, and
> some glue code. Most of those things I had already written for other
> projects. Jikto probably only took me < 24 hours to piece together.
>
>
>
> Anyway, the long and short of all of this is that the code to a web vuln
> scanner written in JavaScript is in the wild now.
>
>
>
> Billy Hoffman
>
> --
>
> Lead Researcher, SPI Labs
>
> SPI Dynamics Inc. – http://www.spidynamics.com
>
> Phone:  678-781-4800
>
> Direct:   678-781-4845


--
pdp (architect) | petko d. petkov
http://www.gnucitizen.org

----------------------------------------------------------------------------
Join us on IRC: irc.freenode.net #webappsec

Have a question? Search The Web Security Mailing List Archives:
http://www.webappsec.org/lists/websecurity/

Subscribe via RSS:
http://www.webappsec.org/rss/websecurity.rss [RSS Feed]