Repository navigation
How do I protect Lua Globals from write access? #185
Description
I'm working with some code, trying to setup a sandbox for running untrusted user code on my server. Currently one of my protections is against endless loops - this is achieved by using Lua's debug.sethook() to call a sanity check every x instructions. unfortunately, sethook() won't accept a POBJECT in place of the function it wants, and this means that I need to set the Python code being called somewhere on the globals. But if a user were to replace this variable with function() end, then my safety check is bypassed.
I've been trying to create some kind of proxy object for the globals table that will protect its entries, but haven't had much luck.
How does one go about this in Lupa?
Activity
scoder commentedon Jun 8, 2021
I'm not sure if there is a way to do this, currently. The security mechanisms are meant to protect the Python side, not the Lua side.
Assuming that Lua doesn't provide a way to control the runtime itself, my guess is that the only safe way to do this is in a separate process that you can kill if it times out.
Did you try using a closure, though? Something like this (untested):
volundmush commentedon Jun 8, 2021
Yeah. I tried the separate thread approach, but it introduces many issues with my game's internal api.
Over on freenode's #lua channel, I heard that the way to do this would be to replace the globals up value with a custom object with a metatable.
How hard would adding some kind of get/set filtering on the globals be, similar to the one used on pyobjects?
guidanoli commentedon Jun 13, 2021
The following Lua code should do the trick.
The
__newindexis triggered every new entry.The
__metatableprevents others from accessing the metatable or overriding it.