Headline
GHSA-jgf4-vwc3-r46v: Directus Allows Single Sign-On User Enumeration
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
- Create a user using a SSO provider
[email protected]. - Try to log-in using the regular login form (or the API)
- When using a valid email address
| APP | API |
|---|---|
- When using an invalid email address
| APP | API |
|---|---|
- 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
Package
npm directus (npm)
Affected versions
>= 9.11, < 10.13.0
Patched versions
10.13.0
Description
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
- Create a user using a SSO provider [email protected].
- Try to log-in using the regular login form (or the API)
- When using a valid email address
APP
API
- When using an invalid email address
APP
API
- 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 directus/directus#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
References
- GHSA-jgf4-vwc3-r46v
- https://nvd.nist.gov/vuln/detail/CVE-2024-39896
- directus/directus@454cb53
br41nslug published to directus/directus
Jul 8, 2024
Published by the National Vulnerability Database
Jul 8, 2024
Published to the GitHub Advisory Database
Jul 8, 2024
Reviewed
Jul 8, 2024
Last updated
Jul 8, 2024