| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SQLAlchemy 1.2.17. It has been rated as critical. This affects an unknown part. This manipulation of the argument group_by as part of Parameter causes sql injection. This vulnerability is tracked as CVE-2019-7548. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in SQLAlchemy 1.2.17. Affected by this vulnerability is an unknown function. The manipulation of the argument group_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 1.2.17 has SQL Injection when the group_by parameter can be controlled.
The bug was discovered 02/01/2019. The weakness was disclosed 02/06/2019 with Microsoft (Website). It is possible to read the advisory at lists.debian.org. This vulnerability is known as CVE-2019-7548 since 02/06/2019. 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 5 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†). The entries VDB-128349, VDB-131035, VDB-131530 and VDB-132134 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/01/2019 🔍02/06/2019 🔍
02/06/2019 🔍
02/07/2019 🔍
03/08/2019 🔍
07/06/2023 🔍
Sources
Advisory: RHSA-2019:0981Organization: Microsoft
Status: Confirmed
CVE: CVE-2019-7548 (🔍)
GCVE (CVE): GCVE-0-2019-7548
GCVE (VulDB): GCVE-100-130627
SecurityFocus: 107400 - Python CVE-2019-9636 Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 02/07/2019 09:38Updated: 07/06/2023 16:52
Changes: 02/07/2019 09:38 (44), 05/09/2020 07:02 (5), 07/06/2023 16:44 (2), 07/06/2023 16:52 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.