Skip to content

Strapi's field level permissions not being respected in relationship title

Moderate severity GitHub Reviewed Published Sep 13, 2023 in strapi/strapi • Updated Sep 25, 2024

Package

npm @strapi/plugin-content-manager (npm)

Affected versions

< 4.12.1

Patched versions

4.12.1

Description

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.

References

@alexandrebodin alexandrebodin published to strapi/strapi Sep 13, 2023
Published to the GitHub Advisory Database Sep 13, 2023
Reviewed Sep 13, 2023
Published by the National Vulnerability Database Sep 15, 2023
Last updated Sep 25, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.056%
(24th percentile)

CVE ID

CVE-2023-37263

GHSA ID

GHSA-m284-85mf-cgrc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.