sequalize up to 1.7.0-alpha2 on Node.js Backslash sql injection

Summaryinfo

A vulnerability marked as critical has been reported in sequalize up to 1.7.0-alpha2 on Node.js. Affected by this vulnerability is an unknown functionality. Performing a manipulation as part of Backslash results in sql injection. This vulnerability is reported as CVE-2016-10554. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in sequalize up to 1.7.0-alpha2 on Node.js (JavaScript Library). It has been classified as critical. This affects an unknown code. The manipulation as part of a Backslash leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS. Before version 1.7.0-alpha3, sequelize defaulted SQLite to use MySQL backslash escaping, even though SQLite uses Postgres escaping.

The bug was discovered 10/31/2016. The weakness was disclosed 05/31/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2016-10554 since 10/29/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 577 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-118436 and VDB-118434 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• JavaScript Library

Name

• sequalize

Version

• 1.7.0-alpha2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion