CVE-2023-36830 json
SQLFluff vulnerability for users with access to config file, using `library_path` to call arbitrary python code.
published 3y ago modified 4mo ago also EUVD-2023-0242 , GHSA-jqhc-m2j3-fjrx , PYSEC-2023-111
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi sqlfluff 2.1.2
- sqlfluff sqlfluff 2.1.2
- sqlfluff Debian 14, Debian 13 2.3.5-1
debian advisories DEBIAN-CVE-2023-36830
Is CVE-2023-36830 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- github.com https://github.com/sqlfluff/sqlfluff/security/advisories/GHSA-jqhc-m2j3-fjrx referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
| GitHub | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | sqlfluff | <2.1.2 |
2.1.2 |
Affected products
- sqlfluff sqlfluff
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
github.com
/sqlfluff/sqlfluff/commit/6cdc38d76bedab4801b035c04d3c2b3aea17de86
web
-
github.com
/sqlfluff/sqlfluff/security/advisories/GHSA-jqhc-m2j3-fjrx
web, exploit, vendor-advisory, advisory
-
github.com
/sqlfluff/sqlfluff/releases/tag/2.1.2
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-36830
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/sqlfluff/PYSEC-2023-111.yaml
web
-
github.com
/sqlfluff/sqlfluff
package
Sources
- CVE List CVE-2023-36830
- GitHub Advisory GHSA-jqhc-m2j3-fjrx
- NVD CVE-2023-36830
- OSV PYSEC-2023-111
- Maintainer advisory GHSA-jqhc-m2j3-fjrx
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of sqlfluff/sqlfluff published their own advisory on GitHub. Reviewed sources take precedence over it.