waterline-sequel 0.50 on Node.js SQL sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability, which was classified as critical, has been found in waterline-sequel 0.50 on Node.js (JavaScript Library). This issue affects an unknown function. The manipulation with an unknown input leads to a sql injection vulnerability (SQL). Using CWE to declare the problem leads to CWE-89. The software 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

waterline-sequel is a module that helps generate SQL statements for Waterline apps Any user input that goes into Waterline's `like`, `contains`, `startsWith`, or `endsWith` will end up in waterline-sequel with the potential for malicious code. A malicious user can input their own SQL statements in waterline-sequel 0.50 that will get executed and have full access to the database.

The bug was discovered 10/31/2016. The weakness was disclosed 05/29/2018 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2016-10551 since 10/29/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 575 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.




CPE 2.3info

CPE 2.2info


VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Name: SQL
Class: Sql injection / SQL
CWE: CWE-89 / CWE-74 / CWE-707
ATT&CK: T1505

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


10/31/2016 🔍
10/29/2017 +363 days 🔍
05/29/2018 +211 days 🔍
05/29/2018 +0 days 🔍
05/30/2018 +1 days 🔍
03/17/2023 +1752 days 🔍


Advisory: 1219
Status: Not defined

CVE: CVE-2016-10551 (🔍)


Created: 05/30/2018 08:48 AM
Updated: 03/17/2023 03:01 PM
Changes: 05/30/2018 08:48 AM (57), 02/09/2020 03:27 PM (1), 03/17/2023 03:01 PM (3)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!