CVE-2020-25032: Flask-Cors Directory Traversal vulnerability

CVE-2020-25032 · Severity: low · CVSS 3.1 · Published 2020-08-31

An issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.

Technologies: Flask-Cors (PyPI). Vendors: PyPI.

Quick answers

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

  • Flask-Cors (PyPI): upgrade to 3.0.9 or later
    pip install "Flask-Cors>=3.0.9"

Affected products

  • Flask-Cors (PyPI) ECOSYSTEM:introduced=0,fixed=3.0.9

Identifiers

  • CVE-2020-25032
  • GHSA-xc3p-ff3m-f46v
  • PYSEC-2020-43

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