Skeptikal.org

Wednesday, July 8, 2009

RIP Milw0rm (or not)

Sadly, Milw0rm.com is going offline- permanently, from the sound of it. Str0ke posted the following message on the site before it went dark:

Well, this is my goodbye header for milw0rm. I wish I had the time I did in the past to post exploits, I just don't :(. For the past 3 months I have actually done a pretty crappy job of getting peoples work out fast enough to be proud of, 0 to 72 hours (taking off weekends) isn't fair to the authors on this site. I appreciate and thank everyone for their support in the past. Be safe, /str0ke


While it gets a bad rap for its large script kiddie user base, I've learned a lot from the exploits on that site, and it will be missed. Thanks Str0ke.

If anybody has info about where I can get a copy of the milw0rm archives, I'd be happy to mirror it here.

Update 7/8/2009 2:47 PM: While Str0ke isn't going to be running things, it looks like he found some other people to take over for him. Exploit submissions are still closed for now, and milw0rm.com is still offline, though that may just be server overloading.

Labels: , ,

Wednesday, May 6, 2009

An Apology to nCircle

In yesterday's post on ASV vulnerabilities, I said that nCircle did not respond to my report and belonged in the doghouse. In fact, they were one of the best, and had the vulnerability fixed within mere minutes of my report. I had lists of good and bad ASVs and they accidentally ended up in the wrong one.

Apologies to nCircle, and thanks to Andrew Storms for pointing it out. I've corrected yesterday's post.

Labels:

Tuesday, May 5, 2009

Most PCI Companies Are Insecure

The McAfee XSS got slashdotted. I think that all this attention is a good thing, putting a spotlight on XSS issues, but I have to say, I'm surprised by it. It's not like XSS attacks are news anymore, and it's not as if this is the first McAfee XSS to be published. Last night, I found an XSS hole in the verification script for their SiteAdvisor service (for extra irony).

McAfee SiteAdvisor XSS

But really, focusing on these XSS holes is missing the point. I never thought I'd say this, but in my experience, McAfee is one of the better ASVs out there. This isn't a compliment to them, it's an insult to the entire industry. Here are a few examples of other ASVs.

Until last week, atsec.com was vulnerable to XSS.

Until last week, secureconnect.com was vulnerable to XSS.

Until last week, ncircle.com was still vulnerable to XSS.

sungard.com is still vulnerable to XSS.

controlcase.com is still vulnerable to XSS.

support.foundstone.com (McAfee's premium brand) is still vulnerable to Cross-site Framing.

Up until a few weeks ago, there were also open redirects on the websites of Qualys, SecurityMetrics, and others. Is it any wonder I'm not at all shocked at a few XSS holes in McAfee's web site?

Some of these companies should be commended for handling the vulnerabilities correctly- nCircle, SecureConnect, Qualys, and even McAfee responded admirably- sometimes the issue was fixed within minutes of my vulnerability report. Others- Foundstone, ControlCase, and Sungard, belong in the doghouse- none of them even responded.

However, the glaring fact is that the entire PCI scanning industry is, frankly, bad at scanning for vulnerabilities. Most of these websites use their own scanning service on their own websites. While I still hold that in-depth audits for these sites should have taken place long ago, the scanners should have caught the problems as well. Some of these domains contain the portals for customers to manage their PCI compliance scans.

People, let's take the focus off of McAfee, and put it where it belongs. The PCI scanning industry as a whole is a joke, and across the board, these Web Security companies are themselves bad at security.

Edit 5-6-2009: nCircle was one of the fast-responders.
I mistakenly listed them as one of the "doghouse" ASVs.

Labels: , , , , , , , ,