CriticalGHSA-hfg2-wf6j-x53pCVE-2012-0805PYSEC-2012-9

SQLAlchemy vulnerable to SQL injection

Published 14 May 2022 · Updated 28 Oct 2024

Is your project on an affected sqlalchemy?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.7.0b4
Fixed in
0.7.0b4
Update to the fixed version for your release line, for example:pip install 'sqlalchemy>=0.7.0b4'

Details

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.

Is GHSA-hfg2-wf6j-x53p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sqlalchemy, and gives you the command that fixes it.

More advisories for sqlalchemy

  • CriticalCVE-2019-7164SQLAlchemy vulnerable to SQL Injection via order_by parameter · 16 Apr 2019
  • CriticalCVE-2019-7548SQLAlchemy is vulnerable to SQL Injection via group_by parameter · 16 Apr 2019
sqlalchemy security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.