Skip to content

Strapi may leak sensitive user information, user reset password, tokens via content-manager views

Moderate severity GitHub Reviewed Published Sep 13, 2023 in strapi/strapi • Updated Nov 11, 2023

Package

npm @strapi/admin (npm)

Affected versions

< 4.11.7

Patched versions

4.11.7
npm @strapi/plugin-content-manager (npm)
< 4.11.7
4.11.7
npm @strapi/utils (npm)
< 4.11.7
4.11.7

Description

Summary

I can get access to user reset password tokens if I have the configure view permissions
b37a6fd9eae06027e7d91266f1908a3d
6c1da5b3bfbb3bca97c8d064be0ecb05

Details

/content-manager/relations route does not remove private fields or ensure that they can't be selected

PoC

Install fresh strapi instance
start up strapi and create an account
create a new content-type
give the content-type a relation with admin users and save
go to Admin panel roles Author and then plugins.
Enable for content-manager collection types the configure view
In the collection time now only give them access to the collection you created for this.
Create a new admin user account with the Author role
Log out and request a password reset for the main admin user.
Login on the newly created account
go to the collection type you created for this test and click the create new entry button,
click in the create new entry view on configure view.
select the admin user relation we created click on resetPasswordToken
Now go back to the create an entry view and when selection the relation we created we now see the reset tokken

Impact

Impact is that the none admin user now has the reset token of the admin users account and can resets its password using that to escalate his privilege's

Still you need the configure view permission to be able to escalate your privilege's

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 Nov 11, 2023

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
High
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:H/PR:L/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.056%
(24th percentile)

Weaknesses

CVE ID

CVE-2023-36472

GHSA ID

GHSA-v8gg-4mq2-88q4

Source code

Credits

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