Directus allows redacted data extraction on the API through "alias"
cve-program · CVE-2024-34708
PublishedDirectus is a real-time API and App dashboard for managing SQL database content. A user with permission to view any collection using redacted hashed fields can get access the raw stored version using the `alias` functionality on the API. Normally, these redacted fields will return `**********` however if we change the request to `?alias[workaround]=redacted` we can instead retrieve the plain text value for the field. This can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them. This vulnerability is fixed in 10.11.0.
Read the publisher's advisoryeuvd · EUVD-2024-1709
PublishedDirectus is a real-time API and App dashboard for managing SQL database content. A user with permission to view any collection using redacted hashed fields can get access the raw stored version using the `alias` functionality on the API. Normally, these redacted fields will return `**********` however if we change the request to `?alias[workaround]=redacted` we can instead retrieve the plain text value for the field. This can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them. This vulnerability is fixed in 10.11.0.
Read the publisher's advisorynvd · CVE-2024-34708
PublishedDirectus is a real-time API and App dashboard for managing SQL database content. A user with permission to view any collection using redacted hashed fields can get access the raw stored version using the `alias` functionality on the API. Normally, these redacted fields will return `**********` however if we change the request to `?alias[workaround]=redacted` we can instead retrieve the plain text value for the field. This can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them. This vulnerability is fixed in 10.11.0.
Read the publisher's advisoryosv · GHSA-p8v3-m643-4xqx
Published## Summary A user with permission to view any collection using redacted hashed fields can get access the raw stored version using the `alias` functionality on the API. Normally, these redacted fields will return `**********` however if we change the request to `?alias[workaround]=redacted` we can instead retrieve the plain text value for the field. ## Steps to reproduce - Set up a simple role with read-access to users. - Create a new user with the role from the previous step - Assign a password to the user The easiest way to confirm this vulnerability is by first visiting `/users/me`. You should be presented with a redacted JSON-object. Next, visit `/users/me?alias[hash]=password`. This time, the returned JSON object will included the raw password hash instead of the redacted value. ## Workaround This can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-34708 · CVE overview and exploitation status
cve-program · CVE-2024-34708
- https://github.com/directus/directus/security/advisories/GHSA-p8v3-m643-4xqx
- https://github.com/directus/directus/commit/e70a90c267bea695afce6545174c2b77517d617b
euvd · EUVD-2024-1709
- https://github.com/directus/directus/security/advisories/GHSA-p8v3-m643-4xqx
- https://github.com/directus/directus/commit/e70a90c267bea695afce6545174c2b77517d617b
nvd · CVE-2024-34708
- https://github.com/directus/directus/commit/e70a90c267bea695afce6545174c2b77517d617b
- https://github.com/directus/directus/security/advisories/GHSA-p8v3-m643-4xqx
osv · GHSA-p8v3-m643-4xqx
Related changes
Linked by CVE identifierNo related changes are available here.