What are the security risks I should guard against when running user-supplied Java code? -
What are the security risks I should guard against when running user-supplied Java code? -
is there comprehensive list of security issues running user-supplied java code on server? i'm already
using timeouts of 10 seconds running code in separate process limited available memory using securitymangager prevent file , network io running code under business relationship extremely limited filesystem permissionsi'm running on freebsd server if matters.
the question i'd inquire myself is, 'how much trust people, , how much trust code won't break system?' in general, reply not much, , not far throw 'em. but, off top of head, here things want guard against.
infinite loops (timeouts help) dodgy i/o operations (trying read/write from/to directories have no access to) privilege escalation code (limiting business relationship able execute in specific context, or specific permissions huge plus) creation of many objects/removing memory (limiting available memory and/or resources plus here) reading/writing from/to socket , not releasing resource expecting input stdin, may problematic if server headlessthere plenty more wary for, tread carefully. safeguard each business relationship , /home
directory 1 best can (a simple chmod 700 $home
it), , experiment code consider dodgy before deploying publicly. 1 time you're comfortable how server holds up, allow others test server , see how goes.
java
Comments
Post a Comment