GHSA-jc55-246c-r88f SurrealDB has an Uncaught Exception Handling Nonexistent Role

• crates.io surrealdb: < 2.1.0 → fixed in 2.1.0 • crates.io surrealdb-core: < 2.1.0 → fixed in 2.1.0

Roles for system users are stored as generic `Ident` values and converted as strings and into the `Role` enum whenever IAM operations are to be performed that require processing the user roles. This conversion expects those identifiers to only contain the values `owner`, `editor` and `viewer` and will return an error otherwise. However, the `unwrap()` method would be called on this result when implementing `std::convert::From for Role`, which would result in a panic where a nonexistent role was used. Impact A privileged user with the `owner` role at any level in SurrealDB would be able to define a user with `DEFINE USER` with an nonexistent role, which would panic when being converted to a `Role` enum in order to perform certain IAM operations with that user. These operations included signing in with the user. This would crash the server, leading to denial of service. Patches Unexistent roles are no longer accepted during parsing when defining a user. Even when successfully associated with a user, referencing unexistent roles will no longer result in a panic and will instead throw an `InvalidRole` error. • Version 2.1.0 and later are not affected by this issue. Workarounds Affected users who are unable to update may want to limit access to users with the `owner` role at any level to trusted parties only. To limit the impact of the denial of service, SurrealDB administrators may also want to ensure that the SurrealDB process is running so that it can be automatically re-started after a crash. Resourcess • #5079 • #5092