Suspended Directus user can continue to use session token to access API
directus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
|
| @directus/types npm |
directus
| Product | Affected | Fixed in |
|---|---|---|
| directus npm |
|
|
| @directus/api npm |
|
|
| @directus/types npm |
≥ 11.0.7 · < 13.0.0
|
Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 10.10.0 and prior to version 11.5.0, a suspended user can use the token generated in session auth mode to access the API despite their status. This happens because there is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. One can extract the session token obtained by, e.g. login in to the app while still active and then, after the user has been suspended continue to use that token until it expires. Version 11.5.0 patches the issue.
From the CVE record · GitHub_M
Directus does not check whether a user is still active when verifying a session token. A suspended user who obtained a token while active can continue using it to access the API until it expires; no further user interaction is described.
Teams running directus >=10.10.0 <11.5.0, @directus/api >=18.0.0 <24.0.1, or @directus/types >=11.0.7 <13.0.0 should check their installations.