I\'m writing some Google Big-query
dynamic reporting utilities to our website, that will allow users to select a parameter to be replaced in the query. Given th
Check "Defense Option 3: Escaping All User Supplied Input" in OWASP:
https://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet#Defense_Option_3:_Escaping_All_User_Supplied_Input
UPDATE: Parametrized queries are an option now
Since the launch of standard SQL in BigQuery, it has been possible to use query parameters as a way of preventing SQL injection. In your query, you can specify named parameters using @
followed by a name, e.g.
SELECT x, y FROM T WHERE x <= @x_max AND y = @target_y;
You can then provide the parameter values through the query_parameters
attribute of the API.