@strapi/plugin-content-manager
Affected
- introduced
0, fixed4.12.1(semver)
Fixed versions
4.12.1
Fix
- Fixed version
4.12.1npm install @strapi/[email protected]
Advisory
Also known as: CVE-2023-37263
Strapi's field level permissions not being respected in relationship title
Summary
Field level permissions not being respected in relationship title.
If I have a relationship title and the relationship shows a field I don't have permission to see I will still be visible.
Details
No RBAC checks on on the relationship the relation endpoint returns
PoC
Setup
Create a fresh strapi instance
Create a new content type
in the newly created content type add a relation to the users-permissions user.
Save.
Create a users-permissions user
Use your created content type and create an entry in it related to the users-permisisons user
Go to settings -> Admin panel -> Roles -> Author
Give the author role full permissions on the content type your created.
Make sure they don't have any permission to see User
Save
Create a new admin account with only the author role
CVE
login on the newly created author acount.
go to the content manager to the colection type you created with the relationship to users_permissions_user
You now see a field you don't have permissions to view.
Impact
RBAC field level checks leaks data selected by the admin user as relationship title
What could be sensitive fields that they should not be allowed to see. by the person having this specific role.
Medium Basis: The source's own band: MODERATE
0, fixed 4.12.1 (semver)4.12.1
4.12.1npm install @strapi/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0