SQLAlchemy vulnerable to SQL Injection via order_by parameter
SQLAlchemy before 1.3.0b3 allows SQL Injection via the order_by parameter. The fix (commit 30307c4) was applied only to the main branch and was never backported to the 1.2.x release line; all 1.2.x versions remain vulnerable.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-7164US | critical9.8 | — | ||
SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter. | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00087.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00010.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00016.htmlWEB
- https://access.redhat.com/errata/RHSA-2019:0981WEB
- https://access.redhat.com/errata/RHSA-2019:0984WEB
- https://github.com/advisories/GHSA-887w-45rq-vxgfADVISORY
- https://github.com/pypa/advisory-database/tree/main/vulns/sqlalchemy/PYSEC-2019-123.yamlWEB
- https://github.com/sqlalchemy/sqlalchemyPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan