surrealdb vulnerabilities and threats

SurrealDB versions before 2.0.4 have a vulnerability where an uncaught exception occurs in the parser error rendering code when processing empty strings. Authorized clients can send malformed queries involving empty string conversions to record, duration, or datetime types, causing a server panic and crash.

SurrealDB versions before 2.1.0 have a denial of service vulnerability triggered by the ORDER BY rand() clause in queries. Authorized clients can cause the server to panic and crash by executing queries that use this sorting mechanism.

SurrealDB versions before 2.1.0 have a denial of service vulnerability where privileged owner users can create users with nonexistent roles. When an attacker signs in with such a user assigned an invalid role, it triggers an uncaught panic that crashes the server.

SurrealDB versions before 2.1.0 have a vulnerability in the rand::time() function where an uncaught exception occurs due to a panic triggered by unwrap on a None result from timestamp_opt. Authorized clients can exploit this to cause repeated server panics, resulting in denial of service.

SurrealDB versions before 2.1.4 have a vulnerability where the DEFINE TABLE ... OVERWRITE clause fails to update table definitions for tables defined with TYPE RELATION. This failure prevents updated permissions from being applied, potentially allowing authorized clients to access data they should no longer have access to.