As such he had shell access. Hence my question still stands .
You do realize that if due to the security issue he was able to execute arbitrary code on the server he could give himself shell access, so whether or not he ended up with shell access is irrelevant since it wasn't the shell access itself that was the access point for the breach, which is exactly what Paul was saying.
This would be like worrying about whether the door to your house is well enough protected when the thief came in from the window but was removing items from the door once they were inside.
This would be like worrying about whether the door to your house is well enough protected when the thief came in from the window but was removing items from the door once they were inside.
I'm only worried about how Santa has been coming in these past few years... we have no Chimney!
BAHAHAHAHAHAHA! Sorry, thought we could use some comic relief in here .
The hack that spawned this thread was only against VB5. VB3 and VB4 were not vulnerable.
That said it is always important to stay up date on the latest patch/version for whatever branch you are using (3.x branch, 4.x branch. or 5.x branch.)
Emails occasionally don't get delivered so it's also a good idea to check the Announcements forum on vBulletin.com or the portal here to keep up with major announcements.