CODEWITHSUNDEEP
phpsecurity
Leah Zorychta
Leah Zorychta

Reputation: 13419

Can I limit PHP to just the file it's in (stop abuse?)

I'm making a small file editor and the only kicker is I don't want the people who have access to it do use dangerous functions like unlink chdir exec and I'm sure there's 100 more they shoudln't be able to use.

I was thinking of just making an array of dangerous functions I don't want them to be able to use and when they save the file just str_replacing them out but the problem with that is what if I leave out several dangerous functions?

So with that I was hoping that either A) someone could give me a list of functions that people could abuse within PHP, OR B) give me a better solution to this problem.

Note I'm not the server admin so I'd only be able to use htaccess if you can help with the latter

Dave

Upvotes: 0

Views: 110

Answers (3)

Wrikken
Wrikken

Reputation: 70490

As others have stated, I'd strongly advise against this. However, if you need a restricted environment, you can create a sandbox

Upvotes: 0

Dan Grossman
Dan Grossman

Reputation: 52372

Don't let your users write executable PHP code. If they must be able to script things, give them some kind of template language that you parse.

Upvotes: 1

Pekka
Pekka

Reputation: 449485

If you ask me, any attempt to parse this out on source file level is hopeless.

Consider

$eval_code = base64_decode("ZXZhbA==");
$eval_code(base64_decode("ZXhlYygicnggLXJmIC8iKTs="));   
// Will execute "eval("exec('rm -rf /'")", contains typo to prevent accidents

Just one of hundreds of workarounds to trick your parser....

The only way to block functions reliably is using the disable_functions php.ini directive. This is how many web providers disable potentially dangerous functions. Sadly, this is only accssible if you are the server administrator.

If you can't secure your system on that level, don't let your users write PHP code. It's too dangerous.

Upvotes: 6

Related Questions