Skip to content
Fencer Intel
critical 9.8

CVE-2012-0805 json

SQLAlchemy vulnerable to SQL injection

published 2012-06-05 14 y ago modified 2026-06-16 4 mo ago also GHSA-hfg2-wf6j-x53p , PYSEC-2012-9 , EUVD-2012-0028

cvss
9.8
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi sqlalchemy 0.7.0, 0.7.0b4
  • sqlalchemy Debian 14, Debian 13, Debian 12 0.6.7-1

debian advisories DEBIAN-CVE-2012-0805

  • python-sqlalchemy RHEL 6 0.5.5-3.el6_2

red hat advisories RHSA-2012:0369

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-0805 updated cvss 4.3

python-sqlalchemy: SQL injection flaw due to not checking LIMIT input for correct type

  • Red Hat Enterprise Linux Server (v. 6) python-sqlalchemy 0.5.5-3.el6_2 Red Hat Enterprise Linux Workstation (v. 6) python-sqlalchemy 0.5.5-3.el6_2
    fixed: vendor fix RHSA-2012:0369

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.83% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • sqlalchemy.org http://www.sqlalchemy.org/trac/changeset/852b6a1a87e7/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi sqlalchemy
<0.7.0b4
<0.7.0
0.7.0b4
0.7.0

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.