Business Logic Errors Affecting python-flask-cors package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-PYTHONFLASKCORS-9509341
- published22 Mar 2025
- disclosed20 Mar 2025
Introduced: 20 Mar 2025
CVE-2024-6844 (opens in a new tab)How to fix?
There is no fixed version for Debian:unstable python-flask-cors.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-flask-cors package and not the python-flask-cors package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.