SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
| Link | Tags |
|---|---|
| https://lists.debian.org/debian-lts-announce/2019/03/msg00020.html | third party advisory mailing list |
| https://access.redhat.com/errata/RHSA-2019:0984 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:0981 | third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00087.html | mailing list third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00010.html | mailing list third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00016.html | mailing list third party advisory vendor advisory |
| https://www.oracle.com/security-alerts/cpujan2021.html | third party advisory patch |
| https://github.com/sqlalchemy/sqlalchemy/issues/4481 | third party advisory exploit |
| https://lists.debian.org/debian-lts-announce/2021/11/msg00005.html | third party advisory mailing list |