The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Implementing CSRF Protection in modifications
With the new version released today for vBulletin 3.6.10 and 3.7.0 RC4, a new protection against Cross Site Request Forgery (CSRF) has been introduced. This new protection might influence the coding in modifications. Scott MacVicar took the time to compile a short explanation on this new protection for the coders on vBulletin.org: Changes for CSRF protection with third party modifications Cross Site Request Forgery (CSRF) involves taking advantage of the stateless nature of HTTP, there are no ways to ensure the exact origin of a request, its also not possible to detect what was actually initiated by a user and what was forced by a third party script. A token was added to the latest version of each of the vBulletin products, with the release of 3.6.10 and 3.7.0 RC4 it is no longer possible to submit a POST request directly without passing in the known token. The addition of a security token for each POST request removes the ability for a remote page to force a user to submit an action. At the moment this protection will only apply to vBulletin files and third party files will need to opt into this protection and add the appropriate hidden field. This was done to preserve backwards compatibility. Adding Protection to your own files To opt your entire file into CSRF protection the following should be added to the top of the file under the define for THIS_SCRIPT. PHP Code:
If this value is set to false then all CSRF protection is removed for the file, this is appropriate for something that intentionally accepts remote POST requests. You should always add this to your file, even if you don't think the script is ever going to receive POST requests. An absence of this defined constant within your files will result in the old style referrer checking being performed. Template Changes The following should be added to all of the forms which POST back to vBulletin or a vBulletin script. This will automatically be filled out with a 40 character hash that is unique to the user. Code:
<input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" /> Exempting Certain Actions It may be appropriate to exempt a particular action from the CSRF protection, in this case you can add the following to the file. PHP Code:
If the skip list needs to be changed at runtime is it available within the registry object, using the init_startup hook the following code would be used to exempt 'example.php?do=action_three'. PHP Code:
|
#32
|
|||
|
|||
Quote:
Thats why I think its now an ajax issue. Ive tried to figure it out but to no avail. The odd thing is, it works fine in 3.6.10, but not in 3.7 RC4 --------------- Added [DATE]1209242134[/DATE] at [TIME]1209242134[/TIME] --------------- problem solved! I had a search around and tried the fix that was being used for a shoutbox. I changed all 3 instances of "securitytoken=" to "&securitytoken=" in vbulletin_global.js and it did the trick! |
#33
|
||||
|
||||
I can't save my vbulletin settings without this error.
What do I change to fix this? In a template? I also can not import any hacks without an error. Where do I fix this? In a template? --------------- Added [DATE]1209251058[/DATE] at [TIME]1209251058[/TIME] --------------- Quote:
I am getting the error when I try to edit a template and save it so this will not work. |
#34
|
||||
|
||||
Note that what you quoted says to "add this line directly after the line containing the above", not directly after that code.
|
#35
|
||||
|
||||
I cannot do anything, including editing templates, turning the board on or loading templates without the security error.
|
#36
|
||||
|
||||
You may want to run the upgrade script again so it makes the necessary changes or run the query listed back on the first page.
|
#37
|
|||
|
|||
I added this line to all my custom templates and followed the instructions as listed.
No errors No problems with any mods casino is still working thank you:up: cmedic |
#38
|
||||
|
||||
Quote:
define('DISABLE_HOOKS', true); |
#39
|
||||
|
||||
Quote:
I've already added the 3 &'s before "securitytoken" in my clienscript/vbulletin_global.js I have also updated ALL my templates per the security token instructions given and still im having problems with every mod that uses java and ajax I am running 3.7 RC4 |
#40
|
||||
|
||||
Quote:
Quote:
Quote:
|
#41
|
|||
|
|||
There have been a few errors in RC4 that have caused problems for a couple of ajax modifications, hence why some have edited vbulletin_global.js. http://www.vbulletin.com/forum/proje...?issueid=25287
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|