The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
I'm thinking of a hack..
..that I need your opinion on, and what vulnerabilities it could possibly cause for the forum.
This hack will create a new large profile field similar to the signature field in the user-profile page. There a user will allow to enter all the web authoring code they want (assume there is no block of which languages they could use), and then this code is stored in the user table as a new column of data, called "custompage". I create a new template, inside the template I place $headinclude, $header, and $footer. Between the $header and $footer I place this variable: $custompage $custompage referes to all the data that the user inputted into their field. Initially, by a link in each users profile, which will look something like: http://www.mysite.com/forums/member.php?s=$session[sessionhash]&action=getcustompage&userid=$userinfo[userid], the member will be sent to a new page that contains all the content they entered in their custompage field. Ofcourse this content will be translated into weblanguage code, and thus displaying that users custom page! Sounds cool, right? Well now I know the uses of HTML on the forum are bad enough for vulnerabilities, so what serious problems would occur allowing this? What comes to my mind ofcourse is malicious users making PHP queries in the field and corrupting my database! Totally possible from my point of view. Other things include calling variables from the global.php, since it is being referenced in members.php, and also calling other variables from members.php. So..to prevent these things, disabling (ofcourse) PHP and other non-HTMl/Javascript languages would probably be a very high priority. As for HTML and javacript itself though, what problems can occur? Any help on this would be great! Regards, Velocd |
#2
|
||||
|
||||
Quote:
|
#3
|
||||
|
||||
surely if you can disable html code in profile fields in member.php currently you could stop it from being used in that field
|
#4
|
||||
|
||||
Quote:
|
#5
|
||||
|
||||
oh... i see what this hack is now ... ...
sounds nice |
#6
|
||||
|
||||
Hmm, I see. Well, the only things that come to mind is somehow disabling certain tags in HTML so you can't use them. But that would be way too hard...I think.
Or..create custom vBulletin tags that act as HTML tags, but again that would be outta line. ...*ponders* Well I'll try to think of some similar hack.. edit: Quote:
|
#7
|
||||
|
||||
how about just banning the malicious html tags thru the "vbulletin options"..
im sure there was a thread on vbulletin.com full of malicious tags... and you could add a little footnote on creation and editing of the page of the tags that cannot be used |
#8
|
||||
|
||||
I'll figure something out..
|
#9
|
||||
|
||||
looking forward to it !
|
#10
|
||||
|
||||
Just a suggestion, but why don't you make it so you have to moderate there custom page and updates to it to check the content of it before visitors can view it?
Just my $0.02. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|