View Full Version : <=1.4.3, 1.5 beta 1 Multiple Vulnerabilities
03-04-2006, 08:48 AM
Sorry for not contacting you before, or not even in a non-public way, but I haven't found any e-mail for this. So here it goes:
Multiple High Risk Vulnerabilities on Pixel Post v1.4.3 and 1.5 beta1 and probably lower versions too.
Please feel free to contact me at: mr.knightmarex [at] gmail [dot] com
03-06-2006, 05:24 AM
If I were a dev I would be a bit cross at not contacting before disclosing publicly - I am sure you are aware of the code of ethics about the sec flaws - Give the vendor enough time to release a patch before disclosure!!
I find the excuse "haven't found any e-mail" a bit lame....
Anyway - don't bother too much about my comments - I just hang here when I have time to waste ;)
We have (dev team) contacted with Mr. Knightmare.
Some of this infos arent really sec holes and some of them are not present in 1.5 BETA1 which we suggest to install from time when it is public.
1.5 RC1 will be patched completle for all known holes.
PS Email address is in code of /index.php so its poor story that there is no info about contact way.
03-06-2006, 09:04 AM
I know you must have done it already - just to be sure search every file for lines like
$var = $_GET['var'];
$var = $_POST['var'];
$var = $_COOKIE['var'];
and put validating functions around the super-globals or cast the super-global into an expected type...
03-07-2006, 07:12 PM
Sure! I did it on purpose! Is that what you wanna hear?
If I would have liked to make bad to you, I would have much better ways of doing it.
It's ok, I recognize it wasn't too good publishing it, but I really didn't see the email on the src code (Too much beer! Or too much time without sleeping) but so it was the only way I figured out to contact you.
If you wanna protect from XSS, there is a good built-in PHP function that protects from this kind of attacks:
And if you wanna allow certaing tags, I don't recommend doing it with strip_tags($var, '<allowed tags>') as it doesn't checks the validity of those allowed tags, and I can also inject code on those tags.
So, probably what would be the best is too apply htmlspecialchars() and then search for exact <b> and so tags, and replace them with valid ones to print them. but be aware also of tags not being closed and so, they wouldn't be a security issue, but they can desfigure the layout.
You can protect from SQL Injections by using the addslashes() or mysql_real_escape_string() functions.
But you should take wether the server doesn't do it automatically by checking with the magic_quotes_gpc() function.
And I would also limit the filetypes that can be uploaded from admin area.
You probably know all this, but well...
I changed php for making it more secure.
I don't know if it is enougth but here this the code :
1) First create a file 'requesttool.php' into the directory include
2) Copy/Paste this function
$get_array_keys = array_keys($_GET);
$_GET[$get_array_keys[$g]] = htmlspecialchars($_GET[$get_array_keys[$g]], ENT_QUOTES);
$post_array_keys = array_keys($_POST);
$_POST[$post_array_keys[$g]] = htmlspecialchars($_POST[$post_array_keys[$g]], ENT_QUOTES);
3) Edit index.php at the root and after this include :
Write this :
Do you thing this right or not ?
03-08-2006, 10:01 PM
I don't think it's a good idea.
First of all, you are still vulnerable to SQL Injection attacks.
That script doesn't secure arrays sent by post or get data. And also it doesn't secure incoming data from cookies or server variables like USER_AGENT.
And also there are sometimes that you don't want to apply htmlspecialchars() cause you don't need it or you need it just as it is. You should apply htmlspecialchars() every time you need to print data that comes from the user.
The function would be good to implement it but with addslashes() and appyling it to arrays also.
Thanks Mr. Knightmare.
I am going to check into google if I don't find a better way to doing that and implement what you talk about.
vBulletin® v3.7.3, Copyright ©2000-2013, Jelsoft Enterprises Ltd.