CVE-2019-7164: SQLAlchemy vulnerable to SQL Injection via order_by parameter

Quick answers

Is CVE-2019-7164 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-7164 being exploited in the wild.

How severe is CVE-2019-7164?

Critical severity, with a CVSS score of 9.8, published 16 April 2019.

Which products and versions are affected?

SQLAlchemy (PyPI) < 1.3.0b3, ECOSYSTEM:introduced=0,fixed=1.3.0b3.

Is there a fix for CVE-2019-7164?

Yes. SQLAlchemy (PyPI): upgrade to 1.3.0b3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2019-7164?

Check whether you run SQLAlchemy (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• SQLAlchemy (PyPI): upgrade to 1.3.0b3 or later

  pip install "SQLAlchemy>=1.3.0b3"

Affected products

• SQLAlchemy (PyPI) < 1.3.0b3, ECOSYSTEM:introduced=0,fixed=1.3.0b3

Identifiers

• CVE-2019-7164
• GHSA-887w-45rq-vxgf
• PYSEC-2019-123

References

• https://api.github.com/users/DEVSOG12
• https://github.com/DEVSOG12
• https://api.github.com/users/DEVSOG12/gists%7B/gist_id%7D
• https://api.github.com/users/DEVSOG12/repos
• https://avatars.githubusercontent.com/u/54543298?v=4
• https://api.github.com/users/DEVSOG12/events%7B/privacy%7D