vBulletin 3.0.5 Released - Critical Update

[assassingod]

http://www.vbulletin.com/forum/showthread.php?t=125480

[high]This is a CRITICAL update[/high]

vBulletin 3.0.5 has been released due to a serious security flaw in all vBulletin 3 versions, including 3.0.4

It is a critical update and is recommended you upgrade immediately .

Important information about the vulnerability can be found in the thread, link at the top of this post:

Important Warning About Sensitive Data

Due to the nature of the vulnerability discovered in vBulletin 3, and as part of our ongoing effort to maximize security, we must assume that one or all of the vBulletin servers may have been compromised.

Therefore, we would STRONGLY RECOMMEND that any customers who may have submitted sensitive data; such as vBulletin admin control panel or server login details, to Jelsoft staff in the past should take steps to alter these details, so that any information that may have been accessed by an unauthorized party could not be used.

Discussion about the thread is here

[lasto]

just done the init.php cant be bothered updating again

yep the one for 3.0.5

[ManagerJosh]

Originally Posted by assassingod

http://www.vbulletin.com/forum/showthread.php?t=125480

[high]This is a CRITICAL update[/high]

vBulletin 3.0.5 has been released due to a serious security flaw in all vBulletin 3 versions, including 3.0.4

It is a critical update and is recommended you upgrade immediately .

Important information about the vulnerability can be found in the thread, link at the top of this post:



Discussion about the thread is here

When can we expect the update to be performed here?

[Mark.B]

This is actually a bit of a poor show.

I've just spent three days rehacking my board for the upgrade to 3.0.4 and now I'm expected to do it all again. And for what? So 3.0.6 can be released days later?

This is the second time in succession that a release of vBulletin has effectively been botched. Everyone is congratulating the team on another release, and I am usually very supportive, but on this occasion there's been a big botch, and for the second time running.

The whole point of purchasing forum software instead of using the free programs is that this sort of messing about should not be neccessary.

[zurih]

Originally Posted by Mark.B

This is actually a bit of a poor show.

I've just spent three days rehacking my board for the upgrade to 3.0.4 and now I'm expected to do it all again. And for what? So 3.0.6 can be released days later?

This is the second time in succession that a release of vBulletin has effectively been botched. Everyone is congratulating the team on another release, and I am usually very supportive, but on this occasion there's been a big botch, and for the second time running.

The whole point of purchasing forum software instead of using the free programs is that this sort of messing about should not be neccessary.

especially when u have a lot of hacks installed.

[strongy]

again, but i just finished fiddling with hacks, it'll have to wait *uploads that init.php though*

[Creative Suite]

woow , We are in era of the speed

, just wanna ask about 3.0.6

[Montadiat.com]

yeah ,

<<< looking out for 3.0.6

[Paul M]

So, the only difference between 3.0.4 and 3.0.5 is init.php ?

[Erwin]

Originally Posted by Mark.B

This is actually a bit of a poor show.

I've just spent three days rehacking my board for the upgrade to 3.0.4 and now I'm expected to do it all again. And for what? So 3.0.6 can be released days later?

This is the second time in succession that a release of vBulletin has effectively been botched. Everyone is congratulating the team on another release, and I am usually very supportive, but on this occasion there's been a big botch, and for the second time running.

The whole point of purchasing forum software instead of using the free programs is that this sort of messing about should not be neccessary.

This is not Jelsoft's fault.

This is a NEW security loophole that is present in ALL vB 3 forums except for the latest version, and is not caused by the release of 3.0.4.

They've just discovered the loophole, that's all. It was already there.

So this has nothing to do with a botched release. It's just coincidental.