https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 01:14:32 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2024-39896 <p>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 &#34;helpful&#34; error that the user belongs to another provider. This vulnerability is fixed in 10.13.0.</p> <p>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 &#34;helpful&#34; error that the user belongs to another provider. This vulnerability is fixed in 10.13.0.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2024-39896 https://vulnerability.circl.lu/vuln/ghsa-jgf4-vwc3-r46v <p><strong>Affected:</strong> npm: directus</p> <p>### 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 &#34;helpful&#34; error that the user belongs to another provider.</p> <p>### Reproduction</p> <p>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</p> <p>| **APP** | **API** | | --- | --- | |  |  |</p> <p>4. When using an invalid email address</p> <p>| **APP** | **API** | | --- | --- | |  |  |</p> <p>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.</p> <p>### 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=&#34;true&#34;`</p> <p>### References Implemented as feature in https://github.com/directus/directus/pull/13184 https://owasp.org/www-project-web-security-testing-gu…</p> <p><strong>Affected:</strong> npm: directus</p> <p>### 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 &#34;helpful&#34; error that the user belongs to another provider.</p> <p>### Reproduction</p> <p>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</p> <p>| **APP** | **API** | | --- | --- | |  |  |</p> <p>4. When using an invalid email address</p> <p>| **APP** | **API** | | --- | --- | |  |  |</p> <p>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.</p> <p>### 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=&#34;true&#34;`</p> <p>### References Implemented as feature in https://github.com/directus/directus/pull/13184 https://owasp.org/www-project-web-security-testing-gu…</p> https://vulnerability.circl.lu/vuln/ghsa-jgf4-vwc3-r46v