Providing an invalid value to the where option of a query caused Sequelize to ignore that option instead of throwing an error.
A finder call like the following did not throw an error:
User.findAll({
where: new Date(),
});
As this option is typically used with plain javascript objects, be aware that this only happens at the top level of this option.
This issue has been patched in <code>sequelize@6.28.1</code> & <code>@sequelize/core@7.0.0.alpha-20</code>
A discussion thread about this issue is open at https://github.com/sequelize/sequelize/discussions/15698
CVE: CVE-2023-22579 Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090
{
"github_reviewed": true,
"cwe_ids": [
"CWE-843"
],
"github_reviewed_at": "2023-02-23T16:58:56Z",
"nvd_published_at": null,
"severity": "CRITICAL"
}