Vulnerability · Published Jul 25, 2023 · Assigned by GitHub_M

CVE-2023-34235Leaking sensitive user information still possible by filtering on private with prefix fields

High 8.6

In plain English

A high-severity information exposure in strapi from strapi. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 1.1% (higher than 66% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.6High
Exploit odds (30 days)1.1%top 34.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

Strapi is an open-source headless content management system. Prior to version 4.10.8, it is possible to leak private fields if one is using the `t(number)` prefix. Knex query allows users to change the default prefix. For example, if someone changes the prefix to be the same as it was before or to another table they want to query, the query changes from `password` to `t1.password`. `password` is protected by filtering protections but `t1.password` is not protected. This can lead to filtering attacks on everything related to the object again, including admin passwords and reset-tokens. Version 4.10.8 fixes this issue.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@strapi/database4.10.8GHSA-9xg4-3qfm-9w8f
npm@strapi/utils4.10.8GHSA-9xg4-3qfm-9w8f

Affected products (as reported)

VendorProductVersions
strapi strapi < 4.10.8

Weakness: CWE-200 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

References