CVE-2023-22578: @sequelize/core Sequelize - Default Support For Vulnerability

CRITICAL
Advisory Identifier: GHSA-f598-mfpv-gmfx
CVSS 10.0
CWE-790
Published
Advisory Summary

CVE-2023-22578 is a CRITICAL (CVSS 10.0) sequelize - default support for vulnerability (CWE-790: Improper Filtering of Special Elements) affecting @sequelize/core libraries in the npm ecosystem. The issue involves sequelize - default support for “raw attributes” when using parentheses. Remediation is available by upgrading affected packages to version 7.0.0-alpha.20, 6.29.0.

CVE-2023-22578 at a Glance

CVE Identifier CVE-2023-22578
GHSA Identifier GHSA-f598-mfpv-gmfx
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-790: Improper Filtering of Special Elements
Affected Product @sequelize/core
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2023-22578

To remediate this vulnerability, upgrade all affected @sequelize/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@sequelize/core fixed: 7.0.0-alpha.20
npm install @sequelize/core@7.0.0-alpha.20
sequelize fixed: 6.29.0
npm install sequelize@6.29.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @sequelize/core

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2023-22578, inspect your project dependencies using npm:

npm ls @sequelize/core

Analyze the terminal output to locate any version of @sequelize/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.0.0-alpha.20), your application is affected.

Note: The npm ls @sequelize/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-790: Improper Filtering of Special Elements, where the product receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component. In @sequelize/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 ```ts User.findAll({ attributes: [ ['count(id)', 'count'] ] }); ``` Produced ```sql 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`](https://github.com/sequelize/sequelize/pull/15374) and [`sequelize@6.29.0`](https://github.com/sequelize/sequelize/pull/15710). In Sequelize 7, it now produces the following: ```sql 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 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 about this issue is open at https://github.com/sequelize/sequelize/discussions/15694 CVE: CVE-2023-22578

CVE-2023-22578 Affected @sequelize/core Versions

2 component(s)
Fixed Versions:
7.0.0-alpha.206.29.0
Product / Package Ecosystem Affected Versions Fixed Version
@sequelize/core
npm
< 7.0.0-alpha.20
7.0.0-alpha.20
sequelize
npm
< 6.29.0
6.29.0

References

Frequently Asked Questions

What is CVE-2023-22578?
CVE-2023-22578 is a security vulnerability in @sequelize/core involving Sequelize - Default support for “raw attributes” when using parentheses under CWE-790: Improper Filtering of Special Elements.
Which @sequelize/core versions are affected?
Affected versions include releases prior to 7.0.0-alpha.20, 6.29.0 across affected packages: @sequelize/core, sequelize.
What version fixes CVE-2023-22578?
Upgrading to 7.0.0-alpha.20, 6.29.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @sequelize/core affected?
Yes, @sequelize/core is affected in releases prior to 7.0.0-alpha.20. Upgrade your dependency to 7.0.0-alpha.20 or later.
Is sequelize affected?
Yes, sequelize is affected in releases prior to 6.29.0. Upgrade your dependency to 6.29.0 or later.
What is the CVSS score of CVE-2023-22578?
CVE-2023-22578 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2023-22578?
CVE-2023-22578 is classified under CWE-790: Improper Filtering of Special Elements (The product receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component.).
How can I check npm dependencies for CVE-2023-22578?
Run the dependency tree command: 'npm ls @sequelize/core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f598-mfpv-gmfx",
  "modified" : "2023-02-24T18:48:49Z",
  "published" : "2023-02-24T18:48:49Z",
  "aliases" : [ "CVE-2023-22578" ],
  "summary" : "Sequelize - Default support for “raw attributes” when using parentheses",
  "details" : "### Impact\n\nSequelize 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\n\n```ts\nUser.findAll({\n  attributes: [\n    ['count(id)', 'count']\n  ]\n});\n```\n\nProduced\n\n```sql\nSELECT count(id) AS \"count\" FROM \"users\"\n```\n\n### Patches\n\nThis feature was deprecated in Sequelize 5, and using it prints a deprecation warning.\n\nThis issue has been patched in [`@sequelize/core@7.0.0.alpha-20`](https://github.com/sequelize/sequelize/pull/15374) and [`sequelize@6.29.0`](https://github.com/sequelize/sequelize/pull/15710). \n\nIn Sequelize 7, it now produces the following:\n\n```sql\nSELECT \"count(id)\" AS \"count\" FROM \"users\"\n```\n\nIn 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.\n\n### Mitigations\n\nDo 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.\n\n---\n\nA discussion thread about this issue is open at https://github.com/sequelize/sequelize/discussions/15694\nCVE: CVE-2023-22578",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@sequelize/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "7.0.0-alpha.20"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "sequelize"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.29.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sequelize/sequelize/security/advisories/GHSA-f598-mfpv-gmfx"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-22578"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sequelize/sequelize/pull/15710"
  }, {
    "type" : "WEB",
    "url" : "https://csirt.divd.nl/CVE-2023-22578"
  }, {
    "type" : "WEB",
    "url" : "https://csirt.divd.nl/DIVD-2022-00020"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sequelize/sequelize"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sequelize/sequelize/discussions/15694"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sequelize/sequelize/releases/tag/v6.29.0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sequelize/sequelize/releases/tag/v7.0.0-alpha.20"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-790" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-02-24T18:48:49Z",
    "nvd_published_at" : null
  }
}