# CVE-2024-28255: Authentication Bypass in OpenMetadata > Attackers can bypass authentication via path manipulation to access protected endpoints, potentially leading to arbitrary code execution. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 15 Mar 2024 - **Updated:** 19 Aug 2024 - **Also known as:** GHSA-6wx7-qw5p-wh84 ## What is CVE-2024-28255? CVE-2024-28255 is a critical authentication bypass vulnerability in open-metadata OpenMetadata, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, 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 `JwtFilter` handles the API authentication by requiring and verifying JWT tokens. When a new request comes in, the request's path is checked against this list. When the request's path contains any of the excluded endpoints the filter returns without validating the JWT. Unfortunately, an attacker may use Path Parameters to make any path contain any arbitrary strings. For example, a request to `GET /api/v1;v1%2fusers%2flogin/events/subscriptions/validation/condition/111` will match the excluded endpoint condition and therefore will be processed with no JWT validation allowing an attacker to bypass the authentication mechanism and reach any arbitrary endpoint, including the ones listed above that lead to arbitrary SpEL expression injection. This bypass will not work when the endpoint uses the `SecurityContext.getUserPrincipal()` since it will return `null` and will throw an NPE. This issue may lead to authentication bypass and has been addressed in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability. This issue is also tracked as `GHSL-2023-237`. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2024-28255? It affects 1 product. Products: Open-Metadata Openmetadata. ## How do I fix CVE-2024-28255? No fix has been published for CVE-2024-28255 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-28255 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28255 exists. Public exploit code: - OpenMetadata_RCE (CVE-2024-28255) Batch scan/exploit (github_poc): https://github.com/YongYe-Security/CVE-2024-28255 - OpenMetadata authentication bypass and SpEL injection exploit chain (metasploit) - OpenMetadata - Authentication Bypass (nuclei): http/cves/2024/CVE-2024-28255.yaml ## Other vulnerabilities in open-metadata OpenMetadata - [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/` 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/` 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-28255 and fix it if it is affected. What it is: CVE-2024-28255 is a critical authentication bypass vulnerability in open-metadata OpenMetadata, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28255 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-28255/ (Markdown: https://insights.sbomify.com/CVE-2024-28255/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28255 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28255 - OSV: https://osv.dev/vulnerability/CVE-2024-28255 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28255/ Summaries are generated and may contain mistakes; the official description above is the record.