Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-v8gg-4mq2-88q4: Strapi may leak sensitive user information, user reset password, tokens via content-manager views

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

ghsa
#nodejs#git#auth
  1. GitHub Advisory Database
  2. GitHub Reviewed
  3. CVE-2023-36472

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 Sep 13, 2023

Package

npm @strapi/admin (npm)

Affected versions

< 4.11.7

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

Summary

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

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

  • GHSA-v8gg-4mq2-88q4
  • https://github.com/strapi/strapi/releases/tag/v4.11.7

Published to the GitHub Advisory Database

Sep 13, 2023

Last updated

Sep 13, 2023

Related news

CVE-2023-36472: Release v4.11.7 · strapi/strapi

Strapi is an open-source headless content management system. Prior to version 4.11.7, an unauthorized actor can get access to user reset password tokens if they have the configure view permissions. The `/content-manager/relations` route does not remove private fields or ensure that they can't be selected. This issue is fixed in version 4.11.7.