# CVE-2024-55238: OpenMetadata SQL Injection

> Attackers can extract database information via SQL injection in the WorkflowDAO interface of OpenMetadata.

- **Severity:** High 7.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-x8pm-wrg2-mqmx

## What is CVE-2024-55238?

CVE-2024-55238 is a high-severity SQL injection vulnerability in n/a, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-55238?

2 open source packages ship an affected version, including org.open-metadata:openmetadata-service. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.open-metadata:openmetadata-service` | Maven | All versions to 1.4.1 | None |
| `org.open-metadata:openmetadata-service` | Maven | All versions to 1.4.1 | None |

Products: Open-Metadata Openmetadata.

## How do I fix CVE-2024-55238?

No fix has been published for CVE-2024-55238 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-55238 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55238 exists.

## Other vulnerabilities in n/a

- [CVE-2024-28255](https://insights.sbomify.com/CVE-2024-28255/): Authentication Bypass in OpenMetadata (critical 9.8)
- [CVE-2024-28253](https://insights.sbomify.com/CVE-2024-28253/): SpEL Injection in `PUT /api/v1/policies` in OpenMetadata (critical 9.4)
- [CVE-2024-28254](https://insights.sbomify.com/CVE-2024-28254/): SpEL Injection in `GET /api/v1/events/subscriptions/validation/condition/<expr>` in OpenMetadata (high 8.8)
- [CVE-2024-28847](https://insights.sbomify.com/CVE-2024-28847/): SpEL Injection in `PUT /api/v1/events/subscriptions` in OpenMetadata (high 8.8)
- [CVE-2024-28848](https://insights.sbomify.com/CVE-2024-28848/): SpEL Injection in `GET /api/v1/policies/validation/condition/<expr>` in OpenMetadata (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55238 and fix it if it is affected.

What it is: CVE-2024-55238 is a high-severity SQL injection vulnerability in n/a, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55238 exists.

Affected packages and fixed versions:
- org.open-metadata:openmetadata-service (Maven): affected all versions up to 1.4.1; no fix listed
- org.open-metadata:openmetadata-service (Maven): affected all versions up to 1.4.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-55238/ (Markdown: https://insights.sbomify.com/CVE-2024-55238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-55238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-55238
- OSV: https://osv.dev/vulnerability/CVE-2024-55238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-55238/
Summaries are generated and may contain mistakes; the official description above is the record.