python-sqlalchemy: SQL injection flaw due to not checking LIMIT input for correct type
Published Jun 5, 2012
9.3
CRITICALCVSS 4.0
EPSS 2.89%
Description
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.
Affected products
No data.
- ≤ 0.7.0
- 0.6.0
- 0.6.0
- 0.6.0
- 0.6.0
- 0.6.1
- 0.6.2
- 0.6.3
- 0.6.4
- 0.6.5
- 0.6.6
- 0.6.7
- 0.7.0
- 0.7.0
No data.
Red Hat Enterprise Linux 6
python-sqlalchemy-0:0.5.5-3.el6_2
Fixed · RHSA-2012:0369
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | python-sqlalchemy-0:0.5.5-3.el6_2 | Fixed | RHSA-2012:0369 |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:L/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (15 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 2.89% (0.02886) | 86.38th | v5 (v2026.06.15) |
| Jun 15, 2026 | 2.86% (0.02862) | 84.89th | v5 (v2026.06.15) |
| Mar 30, 2025 | 1.65% (0.01649) | 80.31th | v4 (v2025.03.14) |
| Mar 29, 2025 | 4.77% (0.04774) | 82.04th | v4 (v2025.03.14) |
| Mar 17, 2025 | 1.65% (0.01649) | 80.74th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.38% (0.00380) | 73.78th | v3 (v2023.03.01) |
| Jun 24, 2024 | 0.38% (0.00380) | 73.04th | v3 (v2023.03.01) |
| Mar 4, 2024 | 0.55% (0.00545) | 76.83th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.66% (0.00656) | 78.83th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.66% (0.00656) | 76.32th | v3 (v2023.03.01) |
| Mar 6, 2023 | 2.17% (0.02172) | 80.77th | v2 (v2022.01.01) |
| Feb 13, 2023 | 2.17% (0.02172) | 80.28th | v2 (v2022.01.01) |
| Feb 3, 2023 | 2.69% (0.02686) | 82.44th | v2 (v2022.01.01) |
| Apr 1, 2022 | 2.17% (0.02172) | 78.91th | v2 (v2022.01.01) |
| Feb 4, 2022 | 2.17% (0.02172) | 57.73th | v2 (v2022.01.01) |
References (20)
- http://rhn.redhat.com/errata/RHSA-2012-0369.html vendor-advisoryx_refsource_REDHAT
- http://secunia.com/advisories/48327 third-party-advisoryx_refsource_SECUNIAVendor Advisory
- http://secunia.com/advisories/48328 third-party-advisoryx_refsource_SECUNIAVendor Advisory
- http://secunia.com/advisories/48771 third-party-advisoryx_refsource_SECUNIAVendor Advisory
- http://www.debian.org/security/2012/dsa-2449 vendor-advisoryx_refsource_DEBIAN
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:059 vendor-advisoryx_refsource_MANDRIVA
- http://www.sqlalchemy.org/changelog/CHANGES_0_7_0 x_refsource_CONFIRM
- http://www.sqlalchemy.org/trac/changeset/852b6a1a87e7 x_refsource_CONFIRMExploitPatch
- https://access.redhat.com/security/cve/CVE-2012-0805 Vendor Advisory
- https://bugs.launchpad.net/keystone/+bug/918608 x_refsource_MISC
- https://bugzilla.redhat.com/show_bug.cgi?id=783305 Issue Tracking
- https://exchange.xforce.ibmcloud.com/vulnerabilities/73756 vdb-entryx_refsource_XF
- https://github.com/advisories/GHSA-hfg2-wf6j-x53p Advisory
- https://github.com/pypa/advisory-database/tree/main/vulns/sqlalchemy/PYSEC-2012-9.yaml
- https://github.com/sqlalchemy/sqlalchemy/commit/51fea2e159ca93daa0bc8066a5c35d8436d99418
- https://nvd.nist.gov/vuln/detail/CVE-2012-0805
- https://web.archive.org/web/20140721183117/http://secunia.com/advisories/48771
- https://web.archive.org/web/20140802043526/http://secunia.com/advisories/48328
- https://web.archive.org/web/20140802044957/http://secunia.com/advisories/48327
- https://www.cve.org/CVERecord?id=CVE-2012-0805
Change history (0)
No recorded changes yet.