Leaking sensitive user information still possible by filtering on private with prefix fields

Description

Still able to leak private fields if using the t(number) prefix

Recommendation

Update the @strapi/utils package to the latest compatible version. Followings are version details:

Affected version(s): <= 4.10.7
Patched version(s): 4.10.8

References

GHSA-9xg4-3qfm-9w8f
CVE-2023-34235
CWE-200
CAPEC-310
OWASP 2021-A1
OWASP 2021-A6

Could your website be exposed too?

SmartScanner can check your website for Leaking sensitive user information still possible by filtering on private with prefix fields and gives you actionable findings to investigate.

Start a free scan

Related Issues

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
Strapi may leak sensitive user information, user reset password, tokens via content-manager views - CVE-2023-36472
Unauthorized Access to Private Fields in User Registration API - @strapi/plugin-users-permissions - CVE-2023-39345

How to Secure your NodeJs Express Javascript Application - part 1

How to Secure your NodeJs Express Javascript Application - part 2

10 Secure Coding Best Practices to Follow in Every Project

See something that needs correcting? Let us knowUpdated November 04, 2023