Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact Sequelize 6.28.2 and prior has a dangerous feature where using parentheses in the attribute option would make Sequelize use the string as-is in the SQL Produced Patches This feature was deprecated in Sequelize 5, and using it prints a deprecation warning. This issue has been patched in @sequelize/core@7.0.0.alpha-20 and sequelize@6.29.0. In Sequelize 7, it now produces the following: In Sequelize 6, it throws an error explaining that we had to introduce a breaking change, and requires the user to explicitly opt-in to either the Sequelize 7 behavior (always escape) or the Sequelize 5 behavior (inline attributes that include () without escaping). See https://github.com/sequelize/sequelize/pull/15710 for more information. Mitigations Do not use user-provided content to build your list or attributes. If you do, make sure that attribute in question actually exists on your model by checking that it exists in the rawAttributes property of your model first. --- A discussion thread…
Recommended action: Upgrade to 7.0.0-alpha.20 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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: 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-20 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
Recommended action: Upgrade to 7.0.0-alpha.20 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Due to improper input filtering in the sequelize js library, can malicious queries lead to sensitive information disclosure.
Recommended action: Upgrade to 7.0.0-alpha.20 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.