Headline
GHSA-pmf4-v838-29hg: Directus allows privilege escalation using Share feature
Summary
When sharing an item, user can specify an arbitrary role. It allows user to use a higher-privileged role to see fields that otherwise the user should not be able to see.
Details
Specifying role on share should be available only for admins. The current flow has a security flaw.
Each other role should allow to share only in the context of the same role. As there is no role hierarchy in Directus, it is impossible to tell which role is higher or lower, so only admins should be able to specify the role for share.
Optionally, instead of specifying a role, shareer* should be able to specify which fields (limited to fields shareer sees) are available on shared item. Similarily to import.
*shareer - a person that creates a share link to item
PoC
- Create a collection with a secret field.
- Create role A that sees the secret field
- Create role B that does not see the secret field, but can use share feature.
- Create item with secret field filled.
- Use account with role B to share the object as role A and gain unauthorized access to secret value.
Here’s video example: https://www.youtube.com/watch?v=DbV4IxbWzN4 I had to upload it to YouTube, because GitHub allows only 10MB videos.
Impact
Impacted are instances that use the share feature and have specific roles hierarchy and fields that are not visible for certain roles.
Summary
When sharing an item, user can specify an arbitrary role. It allows user to use a higher-privileged role to see fields that otherwise the user should not be able to see.
Details
Specifying role on share should be available only for admins. The current flow has a security flaw.
Each other role should allow to share only in the context of the same role. As there is no role hierarchy in Directus, it is impossible to tell which role is higher or lower, so only admins should be able to specify the role for share.
Optionally, instead of specifying a role, shareer* should be able to specify which fields (limited to fields shareer sees) are available on shared item. Similarily to import.
*shareer - a person that creates a share link to item
PoC
- Create a collection with a secret field.
- Create role A that sees the secret field
- Create role B that does not see the secret field, but can use share feature.
- Create item with secret field filled.
- Use account with role B to share the object as role A and gain unauthorized access to secret value.
Here’s video example: https://www.youtube.com/watch?v=DbV4IxbWzN4
I had to upload it to YouTube, because GitHub allows only 10MB videos.
Impact
Impacted are instances that use the share feature and have specific roles hierarchy and fields that are not visible for certain roles.
References
- GHSA-pmf4-v838-29hg
- https://nvd.nist.gov/vuln/detail/CVE-2025-24353
- directus/directus#23716
- directus/directus@e288a43
- https://github.com/directus/directus/releases/tag/v11.2.0
- https://www.youtube.com/watch?v=DbV4IxbWzN4