Directus's session is cached for OpenID and OAuth2 if `redirect` is not used
directus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
directus
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
21.0.122.2.0Directus is a real-time API and App dashboard for managing SQL database content. An unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include redirect query string. This happens because on that endpoint for both OpenId and Oauth2 Directus is using the respond middleware, which by default will try to cache GET requests that met some conditions. Although, those conditions do not include this scenario, when an unauthenticated request returns user credentials. This vulnerability is fixed in 10.13.3 and 11.1.0.
From the CVE record · GitHub_M
Directus can cache a response containing the last authenticated user's credentials on its OpenID or OAuth2 authentication endpoint when the authentication URL lacks a redirect query string. An unauthenticated requester can then access those credentials; no user interaction is described.
Teams running npm directus versions below 10.13.3 or from 11.0.0-rc.1 through versions below 11.1.0, or npm @directus/api versions below 21.0.1 or from 22.0.0 through versions below 22.2.0, should check their deployments.