SQL Injection in sequelize (CVE-2019-10748)
Summary
SQL injection in sequelize (CVE-2019-10748). Successful exploitation can lead to full system takeover. Exploitable via sequelize. Mitigation: upgrade to 5.8.11 or later.
Original description
The description as published by the source.
Affected versions of sequelize are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the MariaDB and MySQL dialects, which may allow attackers to inject SQL statements and execute arbitrary SQL queries.
Recommendation
If you are using sequelize 5.x, upgrade to version 5.8.11 or later.
If you are using sequelize 4.x, upgrade to version 4.44.3 or later.
If you are using sequelize 3.x, upgrade to version 3.35.1 or later.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2019-10748 has been found in sequelize.
Attackers can target a specific entry point like sequelize over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade sequelize to 5.8.11 or later.
If unsure, ask your IT team or search "sequelize CVE-2019-10748" on the vendor's site.
CVE-2019-10748 (sequelize) — CWE-89
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: sequelize
Patched: 5.8.11 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in sequelize. Attackers reach the vulnerable code path via sequelize without authentication.
Check the vendor advisory for the affected versions of sequelize. Attack surface: sequelize.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 5.8.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sequelize' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sequelize' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sequelizeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sequelize to 5.8.11ステージング環境で 5.8.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web snyk.io
- web npmjs.com