Query-filter bypass via invalid top-level where value
Published Feb 16, 2023 · Updated Apr 1, 2025
Type confusion in Sequelize before 6.28.1 and @sequelize/core before 7.0.0-alpha.20 allows remote authenticated users to bypass query filters. The getWhereConditions path accepts a non-plain object as the top-level where option and returns the tautology 1=1 instead of rejecting the invalid value. An application must pass attacker-controlled, non-plain-object input directly as its top-level where value; exploitation exposes every row that the omitted filter would have constrained.
Summary
What happened
Type confusion in Sequelize before 6.28.1 and @sequelize/core before 7.0.0-alpha.20 allows remote authenticated users to bypass query filters. The getWhereConditions path accepts a non-plain object as the top-level where option and returns the tautology 1=1 instead of rejecting the invalid value. An application must pass attacker-controlled, non-plain-object input directly as its top-level where value; exploitation exposes every row that the omitted filter would have constrained.
The record
- CVE
- CVE-2023-22579
- Published
- Feb 16, 2023
- Updated
- Apr 1, 2025
- Vendor
- Sequelize
- Product
- Sequelize
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 16, 2023CVE publishedPublication date reported by the CVE source.
- Apr 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<v7.0.0-alpha.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo