GitHub Advisoryadvisory · npm

GHSA-m284-85mf-cgrc Strapi's field level permissions not being respected in relationship title

MEDIUM Published 2023-09-13 Modified 2023-09-13 Official page ↗
Aliases
CVE-2023-37263
Ecosystem
npm
Packages
@strapi/plugin-content-manager
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
Weaknesses
CWE-200, CWE-400
Reviewed
2023-09-13

Affected packages

• npm @strapi/plugin-content-manager: < 4.12.1 → fixed in 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.

Related

Alias · CVE (1)

  • CVE-2023-37263 Strapi is the an open-source headless content management system. vulnerability

Weakness · CWE (2)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
  • CWE-400 Uncontrolled Resource Consumption weakness

References