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

CVE-2023-37263 → View on GitHub ↗ View on CVE.org ↗ View on NVD ↗

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.

Basic information

Type
reviewed
Severity
medium
Advisory on GitHub
Open advisory ↗
Repository advisory
Open repository advisory ↗
Source code
Browse source ↗
Published (advisory)
2023-09-13 16:31:43 UTC
Updated
2024-09-25 19:21:15 UTC
GitHub reviewed
2023-09-13 16:31:43 UTC
NVD published
2023-09-15 19:15:08 UTC

EPSS Score

Score Percentile
0.09% 26.19%

CVSS Scores

Base score Version Severity Vector
6.8 3.1 —
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.

Identifiers

Type Value
GHSA GHSA-m284-85mf-cgrc ↗
CVE CVE-2023-37263 ↗

CWEs

CWE id Name
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-400 Uncontrolled Resource Consumption

Credits

  • Boegie19 (reporter)
  • derrickmehaffy (remediation_verifier)
  • alexandrebodin (remediation_developer)

Affected packages (1)

Vulnerable version ranges and first patched releases as published by GitHub.

Ecosystem Package Vulnerable range First patched Vulnerable functions
npm @strapi/plugin-content-manager < 4.12.1 4.12.1 —

References

cvelogic Threat Intelligence