Security
Configure the security settings in BoxLang
This segment is where you can configure the security elements of BoxLang under the security
block in the boxlang.json
Allowed File Operation Extensions
An explicit whitelist of file extensions that are allowed to be uploaded - overrides any values in the disallowedWriteExtensions
Individual file extensions may be whitelisted in your Application context like so:
Anything placed in the allowed extensions overrides the disallowed extensions array
Disallowed Imports
An array of regex patterns (case-sensitive) that will try to be matched to imports or to creation of classes. If they match the patterns a security exception wil be thrown.
Disallowed BIFS
An array of BIF names that will be disallowed from execution.
Disallowed Components
An array of Component names that will be disallowed from execution.
Disallowed File Operation Extensions
The list of file extensions that are not allowed to be uploaded. Also enforced by file relocation operations ( e.g. copy/move ). By default, in the CLI and Lambda runtimes, we don't restrict, but you can :)
In Web runtimes, the following extensions are disallowed by default. Unlike other engines this list does not apply to just uploads but applies to File move and copy operations. This is enforced to prevent a bad actor from uploading a file with one extension and being able to copy it to another that is executable.
Note: If you wish to override a single extension you may do so by placing the extension in the allowedFileOperationExtensions
setting in the application:
populateServerSystemScope
This is a boolean flag that, if enabled, will populate the server.system
scope with the Java environment and properties. If disabled, it will not populate them and users will only be able to get environment and properties via the getSystemSetting()
BIF.
Last updated
Was this helpful?