# CVE-2022-25767: Remote Code Execution

> Attackers can achieve remote code execution and read arbitrary files by connecting the library to a malicious database server.

- **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:** 1 May 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w39x-chvm-pj3c

## What is CVE-2022-25767?

CVE-2022-25767 is a critical unsafe deserialization vulnerability in com.bstek.ureport:ureport2-console, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of package com.bstek.ureport:ureport2-console are vulnerable to Remote Code Execution by connecting to a malicious database server, causing arbitrary file read and deserialization of local gadgets.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

2 open source packages ship an affected version, including com.bstek.ureport:ureport2-console. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.bstek.ureport:ureport2-console` | Maven | All versions to 2.2.9 | None |
| `com.bstek.ureport:ureport2-console` | Maven | All versions to 2.2.9 | None |

Products: Ureport2 Project Ureport2.

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

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

## Is CVE-2022-25767 being exploited?

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

## Other vulnerabilities in com.bstek.ureport:ureport2-console

- [CVE-2023-50090](https://insights.sbomify.com/CVE-2023-50090/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25767 is a critical unsafe deserialization vulnerability in com.bstek.ureport:ureport2-console, published on 1 May 2022. 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-25767 in the wild and no public exploit code.

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

## Sources

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

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