Custom scripts security guidelines

Attention: This page is applicable only for customers who use custom scripts.

ADSelfService Plus custom scripts allow synchronization of users' passwords with other providers. However, not sanitizing data sent to custom scripts can lead to adverse security threats including remote code execution. If a end-user with malicious intent were to enter a command in the new password field of password reset or change page, it will success fully run in the machine where ADSelfService Plus server is installed. Ensure you follow these guidelines for all new and existing script commands to avoid security vulnerabilities:

• All custom script files must be placed inside the [Installation_Directory]/Scripts. References to subfolders are not allowed.
• The script command must only contain the filename and arguments in the Advanced Policy Configuration settings.
• The first argument must be a filename with its extension (example: reset.vbs). Only VBScript (.vbs) and PowerShell script (.ps1) are allowed.
• The use of '..' is restricted in the script command.
• Arguments passed to the script will be encoded in Base64 to prevent command injection attacks.

You can use our decoding scripts for VBScript and PowerShell scripts to simplify data sanitization.

Note: Customers who have migrated from builds 6121 and below, please run this DB query to ensure all your custom scripts are safe to use, after implementing the above guidelines:

Update SystemParams set param_value='true' where param_name='CUSTOM_SCRIPT_SAFE_EXECUTION';

If you face any difficulties in these changes, you can disable custom scripts temporarily and contact our support team.