SQLAlchemy up to 1.2.17/1.3.0b2 order_by sql injection

Summaryinfo

A vulnerability identified as critical has been detected in SQLAlchemy up to 1.2.17/1.3.0b2. This vulnerability affects unknown code. This manipulation of the argument order_by as part of Parameter causes sql injection. This vulnerability is registered as CVE-2019-7164. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in SQLAlchemy up to 1.2.17/1.3.0b2 and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation of the argument order_by as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.

The bug was discovered 02/01/2019. The weakness was published 02/20/2019 with Microsoft (Website). It is possible to read the advisory at lists.debian.org. This vulnerability is known as CVE-2019-7164 since 01/29/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. 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 19 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176645 (Debian Security Update for sqlalchemy (DLA 1718-1)).

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

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 107400†). Similar entries are available at VDB-128349, VDB-130627, VDB-131530 and VDB-132134. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• SQLAlchemy

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9
• 1.2.10
• 1.2.11
• 1.2.12
• 1.2.13
• 1.2.14
• 1.2.15
• 1.2.16
• 1.2.17
• 1.3.0b2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion