python-sqlalchemy: SQL Injection when the order_by parameter can be controlled
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| python27:2.7-8000020190410132513.c0efe978 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2019:0981 | 2019-05-07T00:00:00Z |
| python36:3.6-8000020190410133122.593c47b3 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2019:0984 | 2019-05-07T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1718-1 | sqlalchemy security update |
Debian DLA |
DLA-2811-1 | sqlalchemy security update |
EUVD |
EUVD-2019-0133 | SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter. |
Github GHSA |
GHSA-887w-45rq-vxgf | SQLAlchemy vulnerable to SQL Injection via order_by parameter |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 3.5% (3.496% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')