0x4641494c – Fail Patching and Symantec Remote Root Redux!

Those of you who have been reading this for a while, or who are familiar with my work, might remember this: Symantec Web Gateway Remote Root, a little PoC I knocked together based on an exploit Muts from Offensive Security wrote. His PoC, I felt, was a tad unuseable, so I made an attempt at reinventing it :)

So, naturally, Symantec patched this terrible vulnerability. And everyone breathed a sigh of relief.

Or so they thought! Muts revisited it post-patch, and simply found another way to exploit the EXACT SAME FLAW. And when he released the PoC for his “Exploit: Reloaded”, I like to think he took my advice and wrote a better ‘sploit, as his new one is very similar to my “more weaponized” PoC. A bit neater too… Is this a game of one-upmanship? ;)

Without further ado, here is the exploit: Muts Reloaded!

Anyways, I better go off and finish that demo on Cryptfuscate I promised I would write :)

Short Post – Smart 0day Hunting

Ok, ampoule so I had to notice the “Sammy FORGIT” guy dropping exploits all over Packetstorm and Exploit-DB lately. Most of them in WordPress plugins. You can check out the shit he is dropping here – http://packetstormsecurity.org/files/author/9818/

So, patient I had to take a look to see could I notice any “trick” he was using to find ALL THOSE VULNZ! I want the 0day too!

Lets look at two of the exploits as an example – if you look more there IS a discernable pattern, see , I promise you.



Now, what part of both of those is the vuln in?
Now, is this just me, or are both using the Uploadify library?
Could be a coincidence, but I must look deeper! I must find MORE examples of this!

This file explains it:


So it is the “uploadify.php” file that is buggy as hell. Lets find more examples of this!


-> It has “vuln path” of uploadify/upload.php


-> Has “vuln path” uploadify/uploadify.php


-> Has “vuln path” uploadify/custom.php


-> Has “vuln path” uploadify/uploadify.php

So, as you can see, all these use the “Uploadify” PHP library to handle file uploads. This library is the vulnerability that makes ALL these plugins buggy.
ANY software using a vulnerable library like that, is vulnerable to this bug.

So what does this all mean? Well, if you want the 0day to flood in, you should do as Sammy does. Look for libraries a lot of things use, and find vulns in THEM. The product may be secure, but its libraries are likely not. This way, you canhaz ALL the 0day you ever needed.

Now, excuse me while I SVN checkout the entire repo of WordPress plugins :P