Groovy has always been a powerful scripting language. Now with agents (for
example created with Spring AI or Langchain4j) it's becoming
more common to run Groovy scripts from for example Java or Kotlin.

The question is when third-party generated scripts from agents (or just a
script written by other developers)
run these scripts, how to run it safely and securely? For example by not
giving it access to the file system, socket or environment.

I recently read the documentation of GraalVM on sandboxing:

https://www.graalvm.org/latest/security-guide/sandboxing/

There you can have guest code (JavaScript, Python, Wasm etc) that is a
sandbox when started from the JVM/GraalVM. This works because guest
languages
run in a separate VM, truffle VM, where these restriction policies can be
applied.

Groovy as being a JVM language itself, runs natively on the JVM, and is
very much integrated with other JVM languages such as Java. Historically
there have been several approaches to run Groovy restrictly such as:

SecureASTCustomizer
custom classloaders
SecurityManager (now removed from Java)
bytecode rewriting
custom compilation restrictions

Unfortunately, after the removal of the Java Security Manager, there is no
robust, built-in JVM mechanism for securely sandboxing arbitrary Groovy
code.

Are there any plans to allow strong sandboxing for Groovy embedded in
another JVM Language?

Raymond

Reply via email to