Quick answers
- Is CVE-2021-44597 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-44597 being exploited in the wild.
- How severe is CVE-2021-44597?
- Low severity, with a CVSS score of 3.1, published 10 March 2022.
- Which products and versions are affected?
- Gerapy before 0.9.8; gerapy (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.8.
- Is there a fix for CVE-2021-44597?
- Yes. gerapy (PyPI): upgrade to 0.9.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2021-44597 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2021-44597?
- Check whether you run Gerapy or 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.8 or later
pip install "gerapy>=0.9.8"
Technical details
An access control vulnerability (CWE-863) exists in the project_configure function of Gerapy via improper authorization of the spider parameter. The vulnerability is network-accessible without requiring authentication or user interaction. Attackers can exploit this flaw to bypass authorization checks and execute arbitrary code or manipulate project configurations. The vulnerability affects all versions prior to 0.9.8. A patch is available in version 0.9.8 and later.
Affected products
- Gerapy Gerapy before 0.9.8
Identifiers
- CVE-2021-44597
- GHSA-29vr-79w7-p649
- PYSEC-2022-228
Timeline
- 2021-12-02: disclosed
- 2022: patched: Fixed in version 0.9.8
- 2022-03-11: advisory