Information Disclosure in directus (CVE-2024-39896)
Summary
Vulnerability in directus (CVE-2024-39896). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.13.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-39896 has been found in directus.
Risk of unauthorized operations or information disclosure.
What to do: upgrade directus to 10.13.0 or later.
If unsure, ask your IT team or search "directus CVE-2024-39896" on the vendor's site.
CVE-2024-39896 (directus) — CWE-200
Patched: 10.13.0 — apply immediately
Workaround: 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"
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in directus.
Check the vendor advisory for the affected versions of directus.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.13.0.
Workaround: 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"
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'directus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'directus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
directusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
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"`パッチが適用されるまでの応急処置として、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"を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade directus to 10.13.0ステージング環境で 10.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com