We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Providing an invalid value to the where option of a query caused Sequelize to ignore that option instead of throwing an error.
where
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 sequelize@6.28.1 & @sequelize/core@7.0.0.alpha-20
sequelize@6.28.1
@sequelize/core@7.0.0.alpha-20
A discussion thread about this issue is open at #15698
CVE: CVE-2023-22579 Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090
Impact
Providing an invalid value to the
whereoption 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:
As this option is typically used with plain javascript objects, be aware that this only happens at the top level of this option.
Patches
This issue has been patched in
sequelize@6.28.1&@sequelize/core@7.0.0.alpha-20References
A discussion thread about this issue is open at #15698
CVE: CVE-2023-22579
Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090