mlflow up to 2.13.2 UI Panel artifact_location resource consumption

Summaryinfo

A vulnerability marked as problematic has been reported in mlflow up to 2.13.2. Impacted is an unknown function of the component UI Panel. This manipulation of the argument artifact_location causes resource consumption. This vulnerability appears as CVE-2024-6838. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in mlflow up to 2.13.2. It has been declared as problematic. Affected by this vulnerability is an unknown code of the component UI Panel. The manipulation of the argument artifact_location with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

In mlflow/mlflow version v2.13.2, a vulnerability exists that allows the creation or renaming of an experiment with a large number of integers in its name due to the lack of a limit on the experiment name. This can cause the MLflow UI panel to become unresponsive, leading to a potential denial of service. Additionally, there is no character limit in the `artifact_location` parameter while creating the experiment.

It is possible to read the advisory at huntr.com. This vulnerability is known as CVE-2024-6838 since 07/17/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• mlflow

Version

• 2.13.0
• 2.13.1
• 2.13.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion