Is CVE-2016-10556 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-10556 being exploited in the wild.

How severe is CVE-2016-10556?

Low severity, with a CVSS score of 3, published 18 February 2019.

Which products and versions are affected?

sequelize (npm) SEMVER:introduced=0,fixed=3.20.0.

Is there a fix for CVE-2016-10556?

Yes. sequelize (npm): upgrade to 3.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-10556 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-10556?

Check whether you run sequelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-10556: Sequelize SQL injection in array parameter handling

CVE-2016-10556 · Severity: low · CVSS 3 · Published 2019-02-18

Sequelize is a popular Node.js library used by developers to interact with databases such as PostgreSQL, MySQL, and SQL Server. A SQL injection vulnerability in how Sequelize handles array parameters allows attackers to inject arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. This affects applications using Sequelize to build database queries with user-supplied data.

Technologies: sequelize (npm). Vendors: npm.

Quick answers

Is CVE-2016-10556 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-10556 being exploited in the wild.
How severe is CVE-2016-10556?: Low severity, with a CVSS score of 3, published 18 February 2019.
Which products and versions are affected?: sequelize (npm) SEMVER:introduced=0,fixed=3.20.0.
Is there a fix for CVE-2016-10556?: Yes. sequelize (npm): upgrade to 3.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-10556 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-10556?: Check whether you run sequelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

sequelize (npm): upgrade to 3.20.0 or later
```
npm install sequelize@3.20.0
```

Technical details

The vulnerability exists in Sequelize's handling of array parameters in parameterized queries. When arrays are passed as parameter values (e.g., in an IN clause), Sequelize casts them to strings and fails to properly escape the resulting SQL, allowing SQL injection. An attacker can craft malicious array elements containing SQL metacharacters to break out of the intended query context. The flaw affects PostgreSQL, SQLite, and Microsoft SQL Server. The attack requires the application to accept user input and pass it directly to Sequelize's query() method as a replacement parameter. Patches are available in version 3.20.0 and later.

Affected products

Sequelize Sequelize <3.20.0

Identifiers

CVE-2016-10556
GHSA-9c2p-jw8p-f84v

Timeline

2016-03-29: disclosed: Issue reported on GitHub
2016: patched: Fixed in version 3.20.0
2019-02-18: advisory: GHSA-9c2p-jw8p-f84v published

References

https://github.com/sequelize/sequelize/issues/5671

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.