First published: Wed Jun 12 2024(Updated: )
### Summary 1. If a super admin creates a collection where an item in the collection has an association to another collection, a user with the Author Role can see the list of associated items they did not create. They should only see their own items that they created, not all items ever created. ### Details At the top level every collection shows blank items for an Author if they did not create the item. This is ideal and works great. However if you associate one private collection to another private collection and an Author creates a new item. The pull down should not show the admins list of previously created items. It should be blank unitl they add their own items. ### PoC 1. Sign in as Admin. Navigate to content creation. 2. Select a collection and verify you have items you created there. And that they have associations to other protected collections. 3. Verify role permissions for your collections are set to CRUD if user created. 4. Log out and sign in as a unrelated Author. 5. Navigate to content management and verify you see collections built by admin but empty for you (as expected) 6. Create a new item as an Author and see the card appear with attributes to fill out. 7. Use the form pull down for the associations. 8. Notice that protected collection items from Admin appear in drop down. These should be hidden ### Impact Security vulnerability where authors have access to protected data created by admin. This could be passwords emails or any other item created for the admin's collection. See images below for more context Permissions set ![image](https://user-images.githubusercontent.com/364910/265132222-66e85726-5e01-4ad3-901a-809270a7f11b.png) Good at top level no items seen ![image](https://user-images.githubusercontent.com/364910/265132292-d63fa6df-f32d-48a3-80d0-48a651c570a8.png) Drop down in Author login can see Admin data ![image](https://user-images.githubusercontent.com/364910/265132393-8105bae2-b45c-4327-b1c6-da093557e64f.png)
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@strapi/plugin-content-manager | <4.19.1 | 4.19.1 |
Strapi Strapi | <4.19.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-29181 has a medium severity level indicating potential exposure of sensitive data.
To fix CVE-2024-29181, update Strapi to version 4.19.1 or later.
CVE-2024-29181 affects Strapi version lower than 4.19.1, particularly those using the @strapi/plugin-content-manager.
CVE-2024-29181 allows users with the Author Role to view associated items they did not create.
Users with the Author Role in Strapi can be impacted by CVE-2024-29181 due to improper access control.