Denial of Service in sequelize
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-248.
Summary
Versions of `sequelize` prior to 4.44.4 are vulnerable to Denial of Service (DoS). The SQLite dialect fails to catch a `TypeError` exception for the `results` variable. The `results` value may be undefined and trigger the error on a `.map` call. This may allow attackers to submit malicious input that forces the exception and crashes the Node process. The following proof-of-concept crashes the Node process: ``` const Sequelize = require('sequelize'); const sequelize = new Sequelize({ dialect: 'sqlite', storage: 'database.sqlite' }); const TypeError = sequelize.define('TypeError', { name: Sequelize.STRING, }); TypeError.sync({force: true}).then(() => { return TypeError.create({name: "SELECT tbl_name FROM sqlite_master"}); }); ``` ## Recommendation Upgrade to version 4.44.4 or later.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | sequelize (npm) | before 4.44.4 | 4.44.4 | Patch available | GHSA-fw4p-36j9-rrj3 |
- sequelize (npm) Vendor— Affected before 4.44.4 Fixed in 4.44.4 Patch available GHSA-fw4p-36j9-rrj3
Remediation
- Fix · GHSA-fw4p-36j9-rrj3 sequelize (npm) Fixed in 4.44.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fw4p-36j9-rrj3
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences