Impact

This vulnerability only affects users who:

• authorised an application which requested a 'token write' scope.
• or, using frontend-2, created a Personal Access Token (PAT) with 'token write' scope.

When creating a new token an agent needs to authorise the request with an existing token (the 'requesting token'). The requesting token is required to have token write scope in order to generate new tokens.

However, Speckle server was not verifying that other privileges granted to the new token were not in excess of the privileges of the requesting token. A malicious actor could use a token with only token write scope to subsequently generate further tokens with additional privileges.

These privileges would only grant privileges up to the existing privileges of the user. This vulnerability cannot be used to escalate a user's privileges or grant privileges on behalf of other users.

Immediate Action

All operators of Speckle servers should upgrade their server to version >=2.17.6.

Any users who authorised an application with 'token write' scope, or created a token in frontend-2 with 'token write' scope should:

• review existing tokens and permanently revoke any they do not recognise.
• revoke existing tokens and create new tokens.
• review usage of their account for suspicious activity.

Patches

This has been patched as of version 2.17.6.

Workarounds

No workaround exists; operators of Speckle servers are recommended to upgrade.

References

Speckle provided early information about this security vulnerability via our Insider's Channel. If you are maintaining and operating a Speckle Server, we highly recommend you join the Insider's Channel.