First published: Tue Jun 05 2012(Updated: )
Multiple SQL injection vulnerabilities in SQLAlchemy before 0.7.0b4, as used in Keystone, allow remote attackers to execute arbitrary SQL commands via the (1) limit or (2) offset keyword to the select function, or unspecified vectors to the (3) select.limit or (4) select.offset function.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/SQLAlchemy | <0.7.0b4 | 0.7.0b4 |
SQLAlchemy | <=0.7.0 | |
SQLAlchemy | =0.6.0 | |
SQLAlchemy | =0.6.0-beta1 | |
SQLAlchemy | =0.6.0-beta2 | |
SQLAlchemy | =0.6.0-beta3 | |
SQLAlchemy | =0.6.1 | |
SQLAlchemy | =0.6.2 | |
SQLAlchemy | =0.6.3 | |
SQLAlchemy | =0.6.4 | |
SQLAlchemy | =0.6.5 | |
SQLAlchemy | =0.6.6 | |
SQLAlchemy | =0.6.7 | |
SQLAlchemy | =0.7.0-b1 | |
SQLAlchemy | =0.7.0-b2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2012-0805 is considered to be high due to its potential for remote SQL command execution.
To fix CVE-2012-0805, update SQLAlchemy to version 0.7.0b4 or later.
CVE-2012-0805 affects all SQLAlchemy versions prior to 0.7.0b4, including versions 0.6.0 to 0.6.7.
CVE-2012-0805 is classified as an SQL injection vulnerability.
Yes, CVE-2012-0805 can be exploited remotely by attackers to execute arbitrary SQL commands.