Waraxe IT Security Portal

oprime2001 · Beginner

Keeping security in mind, how should variables in third-party modules be "secured" or sanitized? I'd like to be able to check for myself how secure third-party modules are before I introduce them (and any potential security holes) to my websites.

For example, I am thinking of adding Gbook MX 2.0 a guestbook module from http://www.port21.com.mx with samples courtesy of Google. The GbookMX table has the following structure

Heintz · Valuable expert

not secure
[url]modules.php?name=GbookMX&idioma=/../file[/url]

you can include any php extensioned file from server throught this..

and another variable (this one needs register_globals in php ini)
[url]modules.php?name=GbookMX&languageslist=AAAAA[/url]

i haven't found use to them but IMHO this is indication that we are not dealing with secure module here.
and i personally don't like php code mixing with html.. you can bearly understand anything, and only thing that is understandable is check for copyright Confused

.

well.. thats only my opinion.. you make decicions

one option is visiting this site, second is looking for .= operator use on first assignment of variable.. a place where else clause is missing and default values are not assigned.. and ofcourse bad check for info validating (regular expressions etc.), but this is very general... you must read articles about php security.