# CVE-2024-28254: SpEL Injection in `GET /api/v1/events/subscriptions/validation/condition/` in OpenMetadata > Authenticated non-admin users can execute arbitrary system commands via SpEL injection in the event subscription validation endpoint due to missing authorization checks. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** 15 Mar 2024 - **Updated:** 13 Aug 2024 - **Also known as:** GHSA-j86m-rrpr-g8gw ## What is CVE-2024-28254? CVE-2024-28254 is a high-severity code injection vulnerability in open-metadata OpenMetadata, published on 15 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `‎AlertUtil::validateExpression` method evaluates an SpEL expression using `getValue` which by default uses the `StandardEvaluationContext`, allowing the expression to reach and interact with Java classes such as `java.lang.Runtime`, leading to Remote Code Execution. The `/api/v1/events/subscriptions/validation/condition/` endpoint passes user-controlled data `AlertUtil::validateExpession` allowing authenticated (non-admin) users to execute arbitrary system commands on the underlaying operating system. In addition, there is a missing authorization check since `Authorizer.authorize()` is never called in the affected path and, therefore, any authenticated non-admin user is able to trigger this endpoint and evaluate arbitrary SpEL expressions leading to arbitrary command execution. This vulnerability was discovered with the help of CodeQL's Expression language injection (Spring) query and is also tracked as `GHSL-2023-235`. This issue may lead to Remote Code Execution and has been addressed in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2024-28254? It affects 1 product. Products: Open-Metadata Openmetadata. ## How do I fix CVE-2024-28254? No fix has been published for CVE-2024-28254 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-28254 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28254 exists. Public exploit code: - OpenMetadata authentication bypass and SpEL injection exploit chain (metasploit) ## Other vulnerabilities in open-metadata OpenMetadata - [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-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/` in OpenMetadata (high 8.8) - [CVE-2026-22244](https://insights.sbomify.com/CVE-2026-22244/): OpenMetadata Server-Side Template Injection (SSTI) in FreeMarker email templates that leads to RCE (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-28254 and fix it if it is affected. What it is: CVE-2024-28254 is a high-severity code injection vulnerability in open-metadata OpenMetadata, published on 15 Mar 2024. 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-28254 exists. Affected product: open-metadata OpenMetadata. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-28254/ (Markdown: https://insights.sbomify.com/CVE-2024-28254/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28254 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28254 - OSV: https://osv.dev/vulnerability/CVE-2024-28254 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28254/ Summaries are generated and may contain mistakes; the official description above is the record.