Directus allows unauthenticated access to WebSocket events and operations
directus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
|
directus
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
|
Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 11.0.0 and prior to version 11.3.0, when setting `WEBSOCKETS_GRAPHQL_AUTH` or `WEBSOCKETS_REST_AUTH` to "public", an unauthenticated user is able to do any of the supported operations (CRUD, subscriptions) with full admin privileges. This impacts any Directus instance that has either `WEBSOCKETS_GRAPHQL_AUTH` or `WEBSOCKETS_REST_AUTH` set to `public` allowing unauthenticated users to subscribe for changes on any collection or do REST CRUD operations on user defined collections ignoring permissions. Version 11.3.0 fixes the issue.
From the CVE record · GitHub_M
Directus instances with `WEBSOCKETS_GRAPHQL_AUTH` or `WEBSOCKETS_REST_AUTH` set to `public` allow unauthenticated users to perform supported operations with full admin privileges. They can subscribe to changes on any collection or perform REST CRUD operations on user-defined collections without the required permissions.
Check instances running Directus >=11.0.0 <11.3.0 or the npm `@directus/api` package >=22.2.0 <23.2.0.