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