sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| StacklokLabs | sqlite-mcp | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Stackloklabs | Sqlite-mcp |
|
No CVSS v4.0
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 |
|---|---|---|
| First Time appeared |
Stackloklabs
Stackloklabs sqlite-mcp |
|
| Vendors & Products |
Stackloklabs
Stackloklabs sqlite-mcp |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | sqlite-mcp is a Model Context Protocol server for SQLite. Prior to 0.1.2, the default read-only mode can be bypassed through execute_query, which accepts a leading SELECT while the SQLite driver executes trailing statements, and through describe_table, which interpolates the caller-controlled table_name into PRAGMA table_info. Either path can issue ATTACH DATABASE, which opens an attached file read-write despite mode=ro and can make the protected database writable, read other SQLite database files, or create a SQLite-format file at a path writable by the server process. Existing non-empty files that are not SQLite databases are refused and left unchanged. The server has no built-in authentication and listens on all interfaces at :8080 by default, so any client that can reach the port can invoke these tools unless an authenticating proxy is in place. This issue is fixed in version 0.1.2. | |
| Title | sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table | |
| Weaknesses | CWE-863 CWE-89 |
|
| References |
|
|
| Metrics |
cvssV3_1
|