SurrealDB before 2.1.4 Permission Bypass via DEFINE TABLE OVERWRITE
surrealdb
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| surrealdb crates.io |
|
|
| surrealdb-core crates.io |
|
|
surrealdb
| Product | Affected | Fixed in |
|---|---|---|
| surrealdb crates.io |
|
|
| surrealdb-core crates.io |
|
|
SurrealDB before 2.1.4 silently fails to overwrite table definitions when the DEFINE TABLE ... OVERWRITE clause is used on tables defined with TYPE RELATION. Because table definitions include the PERMISSIONS clause, an attempt to tighten a table's permissions via OVERWRITE does not take effect, and the administrator may incorrectly believe the change was applied. As a result, a client authorized to run queries may continue to access data in that table that the updated (but unapplied) permissions were intended to restrict.
From the CVE record · VulnCheck
In SurrealDB before 2.1.4, DEFINE TABLE ... OVERWRITE silently fails to update definitions for tables with TYPE RELATION. If an administrator uses it to tighten permissions, a client authorized to run queries may continue accessing data those permissions were intended to restrict.
Check installations using the crates.io surrealdb or surrealdb-core packages at versions 2.0.0 through 2.1.3.