The pass-through functions are those with names that begin with RAWSQL_ or SCRIPT_.
Under certain circumstances, pass-through expressions could be vectors for SQL injection attacks—that is, an attacker might be able to include malicious commands in them as values. This can happen when the workbook contains a calculation that meets all of these criteria:
The calculation includes a SCRIPT_ or RAWSQL_ function.
The expression uses a value that is passed to the calculation from a parameter in the workbook.
The parameter is typed as a string.
The parameter is the first parameter passed to the calculation.
The parameter is not enclosed in quotation marks.
For example, in the following expression, Parameter 1 might be intended to contain a string value, like small, medium, or large.
RAWSQL_STR([Parameter 1])
However, if a user can set the value of Parameter 1 to arbitrary text, that user could potentially create a SQL injection attack.
Because an expression like this could potentially include malicious commands, it is referred to as an insecure script.
Note the last criterion—that insecure scripts include parameters do not have quotation marks. Consider the following example:
RAWSQL_BOOL("%1", [Parameter 1])
This example does not constitute an insecure script, because the value of Parameter 1 is included in quotation marks, so SQL does not treat the value as a command.
By default, users are not allowed to publish a workbook to Tableau Server that contains an insecure script—that is, a workbook that contains a calculation that meets all of the criteria described earlier. When users attempt to publish the workbook, they see the following response from the server:
"This worksheet contains custom user scripts or SQL with injectable string parameters, which may be vulnerable on the target platform."
Publishing is blocked whether users are trying to publish using Tableau Desktop, the tabcmd publish command, or Publish Workbook in the REST API.
You can allow users to publish workbooks that contain insecure scripts by using the following tsm configuration set command:
tsm configuration set vizqlserver.allow_insecure_scripts true
The vizqlserver.allow_insecure_scripts setting is designed for scenarios where a user might try to use a parameter value to send unauthorized SQL or Rserve commands. To help secure Tableau Server installations, the default setting is false, so that users cannot publish workbooks with insecure scripts. Consider the following points about the vizqlserver.allow_insecure_scripts setting:
If your users never create custom SQL or R expressions, you can make sure that vizqlserver.allow_insecure_scripts is set to false without affecting the ability of your users to publish workbooks.
If your users create calculations that include custom SQL or R expressions, but you do not believe that other users might try to pass commands to the data source, you can enable publishing of insecure scripts (that is, set vizqlserver.allow_insecure_scripts to true).
The vizqlserver.allow_insecure_scripts setting applies to a Tableau Server installation as a whole. If this setting is false, publishing workbooks that contain insecure scripts is blocked for all sites and projects on the server.
RAW or SCRIPT_. Therefore, the vizqlserver.allow_insecure_scripts default value of false does not affect those products.vizqlserver.allow_insecure_scripts is changed to false, and then attempting to access a workbook which was published with insecure scripts prior to the setting being changed.001473396

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.