CVE-2020-7698: Command injection in Gerapy

CVE-2020-7698 · Severity: low · CVSS 3.1 · Published 2020-07-29

This affects the package Gerapy from 0 and before 0.9.3. The input being passed to Popen, via the project_configure endpoint, isn’t being sanitized.

Technologies: gerapy (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-7698 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-7698 being exploited in the wild.
How severe is CVE-2020-7698?
Low severity, with a CVSS score of 3.1, published 29 July 2020.
Which products and versions are affected?
gerapy (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.3, GIT:introduced=0,fixed=e8446605eb2424717418eae199ec7aad573da2d2|ECOSYSTEM:introduced=0,fixed=0.9.3.
Is there a fix for CVE-2020-7698?
Yes. gerapy (PyPI): upgrade to 0.9.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-7698?
Check whether you run gerapy (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

  • gerapy (PyPI): upgrade to 0.9.3 or later
    pip install "gerapy>=0.9.3"

Affected products

  • gerapy (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.3, GIT:introduced=0,fixed=e8446605eb2424717418eae199ec7aad573da2d2|ECOSYSTEM:introduced=0,fixed=0.9.3

Identifiers

  • CVE-2020-7698
  • GHSA-g57j-q48p-9vm2
  • PYSEC-2020-44

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.