Leaking sensitive user information still possible by filtering on private with prefix fields - @strapi/database
- Severity:
- High
Description
Still able to leak private fields if using the t(number) prefix
Recommendation
Update the @strapi/database package to the latest compatible version. Followings are version details:
- Affected version(s): <= 4.10.7
- Patched version(s): 4.10.8
References
Related Issues
- Leaking sensitive user information still possible by filtering on private with prefix fields - CVE-2023-34235
- Strapi leaking sensitive user information by filtering on private fields - CVE-2023-22894
- Strapi may leak sensitive user information, user reset password, tokens via content-manager views - @strapi/utils - CVE-2023-36472
- Unauthorized Access to Private Fields in User Registration API - @strapi/plugin-users-permissions - CVE-2023-39345
You might also like:
- Tags:
- npm
- @strapi/database
Anything's wrong? Let us know Last updated on November 04, 2023