corydolphin flask-cors up to 4.01 Request Path try_match case sensitivity

Summaryinfo

A vulnerability identified as problematic has been detected in corydolphin flask-cors up to 4.01. This vulnerability affects the function try_match of the component Request Path Handler. The manipulation leads to case sensitivity. This vulnerability is documented as CVE-2024-6866. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in corydolphin flask-cors up to 4.01 and classified as problematic. This issue affects the function try_match of the component Request Path Handler. The manipulation with an unknown input leads to a case sensitivity vulnerability. Using CWE to declare the problem leads to CWE-178. The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. Impacted is confidentiality. The summary by CVE is:

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 can lead to significant security vulnerabilities, allowing unauthorized origins to access paths meant to be restricted, resulting in data exposure and potential data leaks.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2024-6866 since 07/17/2024. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 237621 (Debian dla-4197 : python3-flask-cors - security update), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (237621) and EUVD (EUVD-2025-6979). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Social Network Software

Vendor

• corydolphin

Name

• flask-cors

Version

• 4.01

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion