@strapi/database@0.0.0-next.fd9757603c653ca239c45d6e28ab536d2dae0b39 vulnerabilities

Strapi's database layer

Direct Vulnerabilities

Known vulnerabilities in the @strapi/database package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • H
Information Exposure

@strapi/database is a Strapi's database layer

Affected versions of this package are vulnerable to Information Exposure such that 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.

Note:

This can lead to filtering attacks on everything related to the object, including admin passwords and reset-tokens.

How to fix Information Exposure?

Upgrade @strapi/database to version 4.10.8 or higher.

<4.10.8
  • M
Information Exposure

@strapi/database is a Strapi's database layer

Affected versions of this package are vulnerable to Information Exposure by developers, users, or plugins, all of who can make every attribute of a Content-Type public without knowing it. The privateAttributes getter is removed when content types are modified, which can result in any attribute becoming public.

NOTE: If a user mutates the content-type they will not be affected.

How to fix Information Exposure?

Upgrade @strapi/database to version 4.10.8 or higher.

<4.10.8