https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 12 Oct 2026 18:16:04 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-218543 EUVD-2026-218543 https://cve.radiocsirt.org/vuln/euvd-2026-218543 https://cve.radiocsirt.org/vuln/fkie_cve-2023-28443 <p>Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 9.23.3, the `directus_refresh_token` is not redacted properly from the log outputs and can be used to impersonate users without their permission. This issue is patched in version 9.23.3.</p> <p>Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 9.23.3, the `directus_refresh_token` is not redacted properly from the log outputs and can be used to impersonate users without their permission. This issue is patched in version 9.23.3.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-28443 https://cve.radiocsirt.org/vuln/ghsa-8vg2-wf3q-mwv7 <p><strong>Affected:</strong> npm: directus</p> <p>### Summary</p> <p>CWE-532: Insertion of Sensitive Information into Log File discovered in v9.23.1. The `directus_refresh_token` is not redacted properly from the log outputs and can be used to impersonate users without their permission.</p> <p>### Details</p> <p>Using `v9.23.1`, I am seeing that the `directus_refresh_token` is not properly redacted as indicated by https://github.com/directus/directus/blob/7c479c5161639aac466c763b6b958a9524201d74/api/src/logger.ts#L13</p> <p>I&#39;m classifying this as a security vulnerability because if someone has access to the log outputs, for example with a shared Cloud account or Splunk implementation, they could exchange the refresh token using `/auth/refresh` for an access token and use the token to perform actions on behalf of an unsuspecting user. This situation creates issues with accountability and non-repudiation because we can no longer have confidence that actions taken in the application were authorized or even performed by the logged-in user.</p> <p>A couple of examples of this are: - A disgruntled employee deletes all of the data to get even with a target team member before logging off on their last day - Under the guise of their unsuspecting boss, a mischievous engineer uploads _questionable_ images that get displayed on internal or external facing content sites</p> <p>The list could go on but I think these communicate the risk of an internal threat that has access to this information 😆</p> <p>### PoC 1. Set `LOG_STYLE=&#34;raw&#34;` and run Directus v9.23.1 1. Log in to th…</p> <p><strong>Affected:</strong> npm: directus</p> <p>### Summary</p> <p>CWE-532: Insertion of Sensitive Information into Log File discovered in v9.23.1. The `directus_refresh_token` is not redacted properly from the log outputs and can be used to impersonate users without their permission.</p> <p>### Details</p> <p>Using `v9.23.1`, I am seeing that the `directus_refresh_token` is not properly redacted as indicated by https://github.com/directus/directus/blob/7c479c5161639aac466c763b6b958a9524201d74/api/src/logger.ts#L13</p> <p>I&#39;m classifying this as a security vulnerability because if someone has access to the log outputs, for example with a shared Cloud account or Splunk implementation, they could exchange the refresh token using `/auth/refresh` for an access token and use the token to perform actions on behalf of an unsuspecting user. This situation creates issues with accountability and non-repudiation because we can no longer have confidence that actions taken in the application were authorized or even performed by the logged-in user.</p> <p>A couple of examples of this are: - A disgruntled employee deletes all of the data to get even with a target team member before logging off on their last day - Under the guise of their unsuspecting boss, a mischievous engineer uploads _questionable_ images that get displayed on internal or external facing content sites</p> <p>The list could go on but I think these communicate the risk of an internal threat that has access to this information 😆</p> <p>### PoC 1. Set `LOG_STYLE=&#34;raw&#34;` and run Directus v9.23.1 1. Log in to th…</p> https://cve.radiocsirt.org/vuln/ghsa-8vg2-wf3q-mwv7 https://cve.radiocsirt.org/vuln/gsd-2023-28443 gsd-2023-28443 https://cve.radiocsirt.org/vuln/gsd-2023-28443