Flask-Cors Project Flask-Cors vulnerabilities
6 known vulnerabilities affecting flask-cors_project/flask-cors.
Total CVEs
6
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3MEDIUM3
Vulnerabilities
Page 1 of 1
CVE-2024-6866HIGHCVSS 7.5v4.0.12025-03-20
CVE-2024-6866 [HIGH] CWE-178 CVE-2024-6866: corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case
corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case-insensitive due to the use of the `try_match` function, which is originally intended for matching hosts. This results in a mismatch because paths in URLs are case-sensitive, but the regex matching treats them as case-insensitive. This misconfiguration ca
ghsanvdosv
CVE-2024-6844MEDIUMCVSS 5.3v4.0.12025-03-20
CVE-2024-6844 [MEDIUM] CWE-346 CVE-2024-6844: A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to
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 con
ghsanvdosv
CVE-2024-6839MEDIUMCVSS 5.3v4.0.12025-03-20
CVE-2024-6839 [MEDIUM] CWE-41 CVE-2024-6839: corydolphin/flask-cors version 4.0.1 contains an improper regex path matching vulnerability. The plu
corydolphin/flask-cors version 4.0.1 contains an improper regex path matching vulnerability. The plugin prioritizes longer regex patterns over more specific ones when matching paths, which can lead to less restrictive CORS policies being applied to sensitive endpoints. This mismatch in regex pattern priority allows unauthorized cross-origin access to s
ghsanvdosv
CVE-2024-6221HIGH≥ 0, < 4.0.22024-08-18
CVE-2024-6221 [HIGH] CWE-284 Flask-CORS allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default
Flask-CORS allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default
A vulnerability in corydolphin/flask-cors version 4.0.1 allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default, without any configuration option. This behavior can expose private network resources to unauthorized external access,
ghsaosv
CVE-2024-1681MEDIUM≥ 0, < 4.0.12024-04-19
CVE-2024-1681 [MEDIUM] CWE-117 flask-cors vulnerable to log injection when the log level is set to debug
flask-cors vulnerable to log injection when the log level is set to debug
corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tr
ghsaosv
CVE-2020-25032HIGHCVSS 7.5fixed in 3.0.92020-08-31
CVE-2020-25032 [HIGH] CWE-22 CVE-2020-25032: An issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows ../ di
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.
ghsanvdosv