# CVE-2022-31764: Apache ShardingSphere ElasticJob-UI allows RCE via event trace data source JDBC

> Authenticated attackers can achieve remote code execution in Apache ShardingSphere ElasticJob-UI by exploiting a JDBC URL injection vulnerability in the H2 database configuration.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** 6 Feb 2025
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-r5mv-57ph-669q

## What is CVE-2022-31764?

CVE-2022-31764 is a high-severity code injection vulnerability in Apache ShardingSphere ElasticJob-UI, published on 6 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Lite UI of Apache ShardingSphere ElasticJob-UI allows an attacker to perform RCE by constructing a special JDBC URL of H2 database. This issue affects Apache ShardingSphere ElasticJob-UI version 3.0.1 and prior versions. This vulnerability has been fixed in ElasticJob-UI 3.0.2.
The premise of this attack is that the attacker has obtained the account and password. Otherwise, the attacker cannot perform this attack.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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

It affects 1 product.


Products: Apache Shardingsphere Elasticjob-Ui.

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

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

## Is CVE-2022-31764 being exploited?

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

## Other vulnerabilities in Apache ShardingSphere ElasticJob-UI

- [CVE-2022-22733](https://insights.sbomify.com/CVE-2022-22733/): Access-Token in ElasticJob UI causes password disclosure (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31764 is a high-severity code injection vulnerability in Apache ShardingSphere ElasticJob-UI, published on 6 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31764 in the wild and no public exploit code.

Affected product: Apache ShardingSphere ElasticJob-UI. 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-2022-31764/ (Markdown: https://insights.sbomify.com/CVE-2022-31764/index.md)
```

## Sources

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

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