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<&Ident> 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.
References
References
garyhai Reporter
Roles for system users are stored as generic
Identvalues and converted as strings and into theRoleenum whenever IAM operations are to be performed that require processing the user roles. This conversion expects those identifiers to only contain the valuesowner,editorandviewerand will return an error otherwise. However, theunwrap()method would be called on this result when implementingstd::convert::From<&Ident> for Role, which would result in a panic where a nonexistent role was used.Impact
A privileged user with the
ownerrole at any level in SurrealDB would be able to define a user withDEFINE USERwith an nonexistent role, which would panic when being converted to aRoleenum 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
InvalidRoleerror.Workarounds
Affected users who are unable to update may want to limit access to users with the
ownerrole 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.References
References