directus
Affected
- introduced
10.10.0, fixed11.5.0(semver)
Fixed versions
11.5.0
Fix
- Fixed version
11.5.0npm install [email protected]
Advisory
Also known as: CVE-2025-30351
Suspended Directus user can continue to use session token to access API
Summary
Since the user status is not checked when verifying a session token a suspended user can use the token generated in session auth mode to access the API despite their status.
Details
There is a check missing in verifySessionJWT to verify that a user is actually still active and allowed to access the API. Right now 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.
PoC
/auth/refresh call, as that invalidates the sessionAuthorization: Bearer <token>Impact
This weakens the security of suspending users.
Low Basis: The source's own band: LOW
10.10.0, fixed 11.5.0 (semver)11.5.0
11.5.0npm install [email protected]18.0.0, fixed 24.0.1 (semver)24.0.1
24.0.1npm install @directus/[email protected]11.0.7, fixed 13.0.0 (semver)13.0.0
13.0.0npm install @directus/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0