# CVE-2019-10749: SQL Injection in sequelize

> Attackers can execute arbitrary SQL commands via unsanitized JSON path keys in the Postgres dialect of the Sequelize ORM.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2598-2f59-rmhq, SNYK-JS-SEQUELIZE-450222

## What is CVE-2019-10749?

CVE-2019-10749 is a critical SQL injection vulnerability in sequelize, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sequelize before version 3.35.1 allows attackers to perform a SQL Injection due to the JSON path keys not being properly sanitized in the Postgres dialect.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-10749?

2 open source packages ship an affected version, including sequelize. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sequelize` | npm | All versions | 3.35.1 |
| `sequelize` | npm | All versions | 3.35.1 |

Products: Sequelizejs Sequelize.

## How do I fix CVE-2019-10749?

Upgrade sequelize to 3.35.1 or later.

## Is CVE-2019-10749 being exploited?

There is no known exploitation of CVE-2019-10749 in the wild and no public exploit code.

## Other vulnerabilities in sequelize

- [CVE-2023-25813](https://insights.sbomify.com/CVE-2023-25813/): SQL Injection via replacements in sequelize (critical 10.0)
- [CVE-2023-22578](https://insights.sbomify.com/CVE-2023-22578/): Sequalize - Default support for “raw attributes” when using parentheses (critical 10.0)
- [CVE-2023-22579](https://insights.sbomify.com/CVE-2023-22579/): Sequalize - Unsafe fall-through in getWhereConditions (critical 9.9)
- [CVE-2019-10748](https://insights.sbomify.com/CVE-2019-10748/): SQL Injection in sequelize (critical 9.8)
- [CVE-2019-10752](https://insights.sbomify.com/CVE-2019-10752/): SQL Injection in sequelize (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10749 and fix it if it is affected.

What it is: CVE-2019-10749 is a critical SQL injection vulnerability in sequelize, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10749 in the wild and no public exploit code.

Affected packages and fixed versions:
- sequelize (npm): affected all versions; fixed in 3.35.1
- sequelize (npm): affected all versions; fixed in 3.35.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10749/ (Markdown: https://insights.sbomify.com/CVE-2019-10749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10749
- OSV: https://osv.dev/vulnerability/CVE-2019-10749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10749/
Summaries are generated and may contain mistakes; the official description above is the record.