CVE-2024-39896: Directus allows SSO User Enumeration

Published Jul 8, 2024
·
Updated

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 test@directus.io. 2. Try to log-in using the regular login form (or the API) 3. When using a valid email address

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

4. When using an invalid email address

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

5. 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 AUTHDISABLEDEFAULT="true"

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

Other sources

Directus is a real-time API and App dashboard for managing SQL database content. 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. This vulnerability is fixed in 10.13.0.

NVD

Affected Software

2 affected componentsFixes available
npm/directus>=9.11<10.13.0
10.13.0
Monospace Directus Node.js<10.13.0

Event History

Jul 8, 2024
CVE Published
via MITRE·05:27 PM
Data Sourced
via MITRE·05:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:41 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-39896?

The severity of CVE-2024-39896 is classified as a medium risk due to potential user enumeration via SSO methods.

2

How do I fix CVE-2024-39896?

To mitigate CVE-2024-39896, upgrade to Directus version 10.13.0 or later.

3

What types of systems are affected by CVE-2024-39896?

CVE-2024-39896 affects Directus versions between 9.11.0 and 10.12.9 as well as earlier versions.

4

What specific vulnerability does CVE-2024-39896 address?

CVE-2024-39896 addresses the issue of user enumeration when using SSO providers combined with local authentication.

5

Does CVE-2024-39896 impact all SSO providers?

CVE-2024-39896 specifically impacts systems using known SSO providers integrated with Directus.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203