| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| directus | ≥ 10.10.0, < 11.5.0 | 11.5.0 |
| @directus/api | ≥ 18.0.0, < 24.0.1 | 24.0.1 |
| @directus/types | ≥ 11.0.7, < 13.0.0 | 13.0.0 |
| directus | ≥ 10.10.0, < 11.5.0 | 11.5.0 |
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.
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.
/auth/refresh call, as that invalidates the sessionAuthorization: Bearer <token>This weakens the security of suspending users.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン