First published: Tue Feb 19 2019(Updated: )
A vulnerability was found in SQLAlchemy 1.2.17. An SQL Injection when the order_by parameter can be controlled. Upstream issue: <a href="https://github.com/sqlalchemy/sqlalchemy/issues/4481">https://github.com/sqlalchemy/sqlalchemy/issues/4481</a> Upstream patch: <a href="https://github.com/sqlalchemy/sqlalchemy/commit/30307c4616ad67c01ddae2e1e8e34fabf6028414">https://github.com/sqlalchemy/sqlalchemy/commit/30307c4616ad67c01ddae2e1e8e34fabf6028414</a>
Affected Software | Affected Version | How to fix |
---|---|---|
SQLAlchemy |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1678520 is classified as critical due to the potential for SQL injection exploitation.
To fix REDHAT-BUG-1678520, upgrade SQLAlchemy to a patched version that addresses the SQL injection vulnerability.
REDHAT-BUG-1678520 affects any systems using SQLAlchemy version 1.2.17.
Yes, exploiting REDHAT-BUG-1678520 can allow attackers to execute unauthorized SQL queries, potentially leading to data breaches.
As of now, there is no specific known exploit publicly documented for REDHAT-BUG-1678520, but the risk remains due to its critical nature.