SQLBot 1.10.0 through 1.10.3 PostgreSQL Dangerous-Function Denylist Bypass via Key Mismatch
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| dataease | SQLBot | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dataease | Sqlbot |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dataease
Dataease sqlbot |
|
| Vendors & Products |
Dataease
Dataease sqlbot |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL dangerous-function denylist because DS_SPECIFIC_DANGEROUS_FUNCTIONS uses 'postgresql' while lookups use the 'pg' type. Authenticated users can steer LLM-generated SQL past check_sql_read() using pg_read_file, pg_write_file, lo_import or lo_export to read or write files on the database host. | |
| Title | SQLBot 1.10.0 through 1.10.3 PostgreSQL Dangerous-Function Denylist Bypass via Key Mismatch | |
| Weaknesses | CWE-184 | |
| References |
|
|
| Metrics |
cvssV3_1
|