CVE-2023-48218 Strapi Protected Populate Plugin leaking fields if the request fields where empty or only fields selected where not populatable
MediumCVSS 5.3
EPSS 0.60%
- Published
- Updated
- Exploit status
- No public exploit known
Description
The Strapi Protected Populate Plugin protects get endpoints from revealing too much information. Prior to version 1.3.4, users were able to bypass the field level security. Users who tried to populate something that they didn't have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds.
Upgrade path
3 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| npm strapi-plugin-protected-populate(npm) | < 1.3.4 | 1.3.4 | Fixed |
| strapi protected populate | < 1.3.4 | 1.3.4 | Fixed |
| strapi-community strapi-plugin-protected-populate | = < 1.3.4 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| npm strapi-plugin-protected-populate(npm) | < 1.3.4 | 1.3.4 |
| strapi-community strapi-plugin-protected-populate | = < 1.3.4 | No fix listed |
| strapi protected populate | < 1.3.4 | 1.3.4 |
References
- https://github.com/strapi-community/strapi-plugin-protected-populate/security/advisories/GHSA-6h67-934r-82g7 vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/strapi-community/strapi-plugin-protected-populate/commit/05441066d64e09dd55937d9f089962e9ebe2fb39 patch
- https://github.com/strapi-community/strapi-plugin-protected-populate/releases/tag/v1.3.4 release-notes
- github.com
- github.com product