Unsafe fall-through in getWhereConditions
### Impact 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: ```ts 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. ### Patches This issue has been patched in [`sequelize@6.28.1`](https://github.com/sequelize/sequelize/pull/15699) & [`@sequelize/core@7.0.0.alpha-20`](https://github.com/sequelize/sequelize/pull/15375) ### References 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
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-22579US | high8.8 | — | ||
Due to improper parameter filtering in the sequalize js library, can a attacker peform injection. | ||||
references
External citations — patches, advisories, analysis.
- https://csirt.divd.nl/CVE-2023-22579WEB
- https://csirt.divd.nl/DIVD-2022-00020WEB
- https://github.com/sequelize/sequelizePACKAGE
- https://github.com/sequelize/sequelize/discussions/15698WEB
- https://github.com/sequelize/sequelize/pull/15375WEB
- https://github.com/sequelize/sequelize/pull/15699WEB
- https://github.com/sequelize/sequelize/releases/tag/v6.28.1WEB
- https://github.com/sequelize/sequelize/releases/tag/v7.0.0-alpha.20WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan