Advisory

GHSA-jgf4-vwc3-r46v

Also known as: CVE-2024-39896

Summary

Directus Allows Single Sign-On User Enumeration

Details

Impact
When relying on SSO providers in combination with local authentication it can be possible to enumerate existing SSO users in the instance. This is possible because if an email address exists in Directus and belongs to a known SSO provider then it will throw a "helpful" error that the user belongs to another provider.

Reproduction

  1. Create a user using a SSO provider [email protected].
  2. Try to log-in using the regular login form (or the API)
  3. When using a valid email address

| APP | API |
| --- | --- |
| image | image |

  1. When using an invalid email address

| APP | API |
| --- | --- |
| image | image |

  1. Using this differing error it is possible to determine whether a specific email address is present in the Directus instance as an SSO user.

Workarounds
When only using SSO for authentication then you can work around this issue by disabling local login using the following environment variable AUTH_DISABLE_DEFAULT="true"

References
Implemented as feature in https://github.com/directus/directus/pull/13184
https://owasp.org/www-project-web-security-testing-guide/v42/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-07-08 18:41 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

directus

npm · All systems

Affected

  • introduced 9.11, fixed 10.13.0 (ecosystem)

Fixed versions

10.13.0

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences