CVE-2024-28848
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `CompiledRule::validateExpression` method evaluates an SpEL expression using an `StandardEvaluationContext`, allowing the expression to reach and interact with Java classes such as `java.lang.Runtime`, leading to Remote Code Execution. The `/api/v1/policies/validation/condition/<expression>` endpoint passes user-controlled data `CompiledRule::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-236`. This issue may lead to Remote Code Execution and has been resolved in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenMetadata before 1.2.4 contains a SpEL expression injection vulnerability in the CompiledRule::validateExpression method. The /api/v1/policies/validation/condition/<expression> endpoint passes user input directly to SpEL evaluation using StandardEvaluationContext, allowing access to dangerous Java classes like java.lang.Runtime for arbitrary command execution. Additionally, the affected endpoint lacks authorization checks since Authorizer.authorize() is never invoked, enabling any authenticated non-admin user to trigger the RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenMetadata versionCheck the version via the OpenMetadata API at /api/v1/system/version or inspect the deployed OpenMetadata JAR/WAR file or Docker container image tagAffected if Version is below 1.2.4 (e.g., 1.2.3, 1.2.2, 1.2.1, 1.2.0, earlier releases)
-
Confirm the vulnerable endpoint is exposedVerify the /api/v1/policies/validation/condition/ endpoint is reachable by sending a test request to your OpenMetadata serverAffected if The endpoint responds and accepts input (indicating the API is exposed)
-
Verify authentication statusCheck whether OpenMetadata authentication is enabled by reviewing the security configuration or testing endpoint access without credentialsAffected if Authentication is enabled and you have any valid user credentials (including non-admin users)
-
Check for policy validation featureInspect whether the Policy service and validation feature are enabled in your OpenMetadata deployment configurationAffected if The Policy feature is active and the validation endpoint is accessible
You are affected if running OpenMetadata version 1.2.3 or earlier AND the /api/v1/policies/validation/condition/ endpoint is accessible to authenticated users, as the vulnerability allows arbitrary SpEL execution without admin privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.4
Upgrade OpenMetadata to version 1.2.4 or later. No workarounds are available.
1.2.4
- Upgrade OpenMetadata to version 1.2.4 or later to remediate this vulnerability
- Verify the upgrade was successful by checking the installed OpenMetadata version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28848 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data