🚨 [security] Update sequelize: 6.25.7 → 6.29.3 (minor)

[depfu[bot]]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sequelize (6.25.7 → 6.29.3) · Repo

Security Advisories 🚨

🚨 Sequelize - Default support for “raw attributes” when using parentheses

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

User.findAll({
  attributes: [
    ['count(id)', 'count']
  ]
});

Produced

SELECT count(id) AS "count" FROM "users"

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:

SELECT "count(id)" AS "count" FROM "users"

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 #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 about this issue is open at #15694
CVE: CVE-2023-22578

🚨 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:

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 & @sequelize/core@7.0.0.alpha-20

References

A discussion thread about this issue is open at #15698

CVE: CVE-2023-22579
Snyk: https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090

🚨 Sequelize information disclosure vulnerability

Due to improper input filtering in the sequelize js library, can malicious queries lead to sensitive information disclosure.

Release Notes

6.29.3

6.29.3 (2023-03-10)

Bug Fixes

• fix unnamed dollar string detection (#15759) (5bda2ce)

6.29.2

6.29.2 (2023-03-09)

Bug Fixes

• postgres: escape identifier in createSchema and dropSchema (#15752) (1ad9a64), closes #15651 #14999

6.29.1

6.29.1 (2023-03-07)

Bug Fixes

• postgres: make sync not fail when trying to create existing enum (#15718) (1b94462)

6.29.0

6.29.0 (2023-02-23)

Features

• throw an error if attribute includes parentheses (fixes CVE-2023-22578) (#15710) (d3f5b5a)

6.28.2

6.28.2 (2023-02-22)

Bug Fixes

• accept undefined in where (#15703) (13f2e89)

6.28.1

6.28.1 (2023-02-21)

Bug Fixes

• throw if where receives an invalid value (#15699) (d9e0728)
• update moment-timezone version (#15685) (48d6193)

6.28.0

6.28.0 (2022-12-20)

Features

• types: use retry-as-promised types for retry options to match documentation (#15484) (fd4afa6)

6.27.0

6.27.0 (2022-12-12)

Features

• add support for bigints (backport of #14485) (#15413) (1247c01)

6.26.0

6.26.0 (2022-11-29)

Features

• postgres: add support for lock_timeout [#15345] (#15355) (94beace)

6.25.8

6.25.8 (2022-11-22)

Bug Fixes

• oracle: remove hardcoded maxRows value (#15323) (7885000)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 12 commits:

• fix: fix unnamed dollar string detection (#15759)
• fix(postgres): escape identifier in createSchema and dropSchema (#15752)
• fix(postgres): make sync not fail when trying to create existing enum (#15718)
• feat: throw an error if attribute includes parentheses (fixes CVE-2023-22578) (#15710)
• meta: fix null test getWhereConditions (#15705)
• fix: accept undefined in where (#15703)
• fix: throw if where receives an invalid value (#15699)
• fix: update moment-timezone version (#15685)
• feat(types): use retry-as-promised types for retry options to match documentation (#15484)
• feat: add support for bigints (backport of #14485) (#15413)
• feat(postgres): add support for lock_timeout [#15345] (#15355)
• fix(oracle): remove hardcoded maxRows value (#15323)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu[bot]]

Closed in favor of #33.