SQLFluff is a SQL linter. Prior to version 2.1.2, in environments where
untrusted users have access to the config files, there is a potential
security vulnerability where those users could use the `library_path`
config value to allow arbitrary python code to be executed via macros. For
many users who use SQLFluff in the context of an environment where all
users already have fairly escalated privileges, this may not be an issue –
however in larger user bases, or where SQLFluff is bundled into another
tool where developers still wish to give users access to supply their on
rule configuration, this may be an issue.
The 2.1.2 release offers the ability for the `library_path` argument to be
overwritten on the command line by using the `–library-path` option. This
overrides any values provided in the config files and effectively prevents
this route of attack for users which have access to the config file, but
not to the scripts which call the SQLFluff CLI directly. A similar option
is provided for the Python API, where users also have a greater ability to
further customise or override configuration as necessary. Unless
`library_path` is explicitly required, SQLFluff maintainers recommend using
the option `–library-path none` when invoking SQLFluff which will disable
the `library-path` option entirely regardless of the options set in the
configuration file or via inline config directives. As a workaround,
limiting access to – or otherwise validating configuration files before
they are ingested by SQLFluff will provides a similar effect and does not
require upgrade.Read More