Unsafe fall-through in getWhereConditions

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.

A discussion thread about this issue is open at sequelize/sequelize#15698

ephys published to sequelize/sequelize Feb 21, 2023

Published to the GitHub Advisory Database Feb 23, 2023

Reviewed Feb 23, 2023

Last updated Feb 23, 2023

Provide feedback