GHSA-7wq3-jr35-275c Directus `search` query parameter allows enumeration of non permitted fields

• npm directus: >= 9.0.0-alpha.4, < 11.5.0 → fixed in 11.5.0

Summary The `search` query parameter allows users with access to a collection to filter items based on fields they do not have permission to view. This allows the enumeration of unknown field contents. Details The searchable columns (numbers & strings) are not checked against permissions when injecting the `where` clauses for applying the search query. This leads to the possibility of enumerating those un-permitted fields. PoC • Create a collection with a string / numeric field, configure the permissions for the public role to not include the field created • Create items with identifiable content in the not permitted field • Query the collection and include the field content in the `search` parameter • See that results are returned, even tho the public user does not have permission to view the field content Impact This vulnerability is a very high impact, as for example Directus instances which allow public read access to the user avatar are vulnerable to have the email addresses, password hashes and potentially admin level access tokens extracted. The admin token and password hash extraction have a caveat, as string fields are only searched with a lower cased version of the search query.