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.
References
Link | Resource |
---|---|
https://github.com/corydolphin/flask-cors/releases/tag/3.0.9 | Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00028.html | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00032.html | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00039.html | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00048.html | Mailing List Third Party Advisory |
https://www.debian.org/security/2020/dsa-4775 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Information
Published : 2020-08-30 21:15
Updated : 2022-04-28 11:28
NVD link : CVE-2020-25032
Mitre link : CVE-2020-25032
JSON object : View
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Products Affected
debian
- debian_linux
opensuse
- backports_sle
- leap
flask-cors_project
- flask-cors