OpenMetadata up to 1.4.1 WorkflowDAO Interface listCount workflowtype/status sql injection

Summaryinfo

A vulnerability identified as critical has been detected in OpenMetadata up to 1.4.1. Impacted is the function listCount of the component WorkflowDAO Interface. Performing a manipulation of the argument workflowtype/status results in sql injection. This vulnerability is known as CVE-2024-55238. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in OpenMetadata up to 1.4.1. It has been classified as critical. This affects the function listCount of the component WorkflowDAO Interface. The manipulation of the argument workflowtype/status with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

OpenMetadata <=1.4.1 is vulnerable to SQL Injection. An attacker can extract information from the database in function listCount in the WorkflowDAO interface. The workflowtype and status parameters can be used to build a SQL query.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-55238 since 12/06/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/24/2025). The attack technique deployed by this issue is T1505 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

• OpenMetadata

Version

• 1.4.0
• 1.4.1

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