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.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
| Link | Tags |
|---|---|
| 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 vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00032.html | mailing list third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00039.html | mailing list third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00048.html | mailing list third party advisory vendor advisory |
| https://www.debian.org/security/2020/dsa-4775 | third party advisory vendor advisory |