CVE-2019-10749

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

published October 29, 2019

CVSS
—
EPSS
1%
Percentile
68.6
In the wild
Unconfirmed
What it is

⚠️ A SQL injection vulnerability lurks in Sequelize versions before 3.35.1, allowing attackers to sneak in malicious payloads through unsanitized JSON path keys. 😱 Think of it like a restaurant where the chef accepts any custom order without checking for allergens—one wrong ingredient can lead to a disastrous meal! An attacker could exploit this flaw to manipulate database queries, potentially gaining access to sensitive data and wreaking havoc on your application's backend. The consequences can be severe, leading to data breaches and loss of user trust—a recipe for disaster!

Put simply

Think of it like a restaurant where the chef accepts any custom order without checking for allergens—one wrong ingredient can lead to a disastrous meal! This vulnerability stems from a lack of proper sanitization for JSON path keys in the PostgreSQL dialect of Sequelize, which can allow attackers to inject malicious SQL code into queries.

What to do

An attacker could exploit this flaw to manipulate database queries, potentially gaining access to sensitive data and wreaking havoc on your application's backend. The consequences can be severe, leading to data breaches and loss of user trust—a recipe for disaster! To secure your application, upgrade to Sequelize version 3.35.1 or later to patch this vulnerability. Additionally, review and sanitize all inputs to your database to ensure no similar issues persist. Regular audits will help you stay ahead of the game! You've got this! With a quick upgrade and some input validation, your app will be much safer in no time. 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01228 · 68.6th percentile
Published
2019-10-29T16:06Z
EPSS history
Timeline
  • 29 OCT 16:06Z
    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
    cvelistv5