# CVE-2022-25894: Remote Code Execution in com.bstek.uflo:uflo-core

> Attackers can execute arbitrary code via improper input validation in the uflo-core Java library's expression evaluation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2023
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-8m9f-c5p9-wqch

## What is CVE-2022-25894?

CVE-2022-25894 is a critical code injection vulnerability in com.bstek.uflo:uflo-core, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package com.bstek.uflo:uflo-core are vulnerable to Remote Code Execution (RCE) in the ExpressionContextImpl class via jexl.createExpression(expression).evaluate(context); functionality, due to improper user input validation.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-25894?

2 open source packages ship an affected version, including com.bstek.uflo:uflo-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.bstek.uflo:uflo-core` | Maven | All versions to 2.1.5 | None |
| `com.bstek.uflo:uflo-core` | Maven | All versions to 2.1.5 | None |

Products: Uflo Project Uflo.

## How do I fix CVE-2022-25894?

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

## Is CVE-2022-25894 being exploited?

There is no known exploitation of CVE-2022-25894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25894 and fix it if it is affected.

What it is: CVE-2022-25894 is a critical code injection vulnerability in com.bstek.uflo:uflo-core, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25894 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.bstek.uflo:uflo-core (Maven): affected all versions up to 2.1.5; no fix listed
- com.bstek.uflo:uflo-core (Maven): affected all versions up to 2.1.5; 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-2022-25894/ (Markdown: https://insights.sbomify.com/CVE-2022-25894/index.md)
```

## Sources

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

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