# CVE-2022-45136: Apache Jena SDB allows arbitrary deserialisation via JDBC

> Attackers can achieve remote code execution in applications using Apache Jena SDB by controlling JDBC connections or database responses.

- **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:** Yes
- **Published:** 14 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-45136, GHSA-g2qw-6vrr-v6pq, UBUNTU-CVE-2022-45136

## What is CVE-2022-45136?

CVE-2022-45136 is a critical unsafe deserialization vulnerability in Apache Jena SDB, published on 14 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Jena SDB 3.17.0 and earlier is vulnerable to a JDBC Deserialisation attack if the attacker is able to control the JDBC URL used or cause the underlying database server to return malicious data. The mySQL JDBC driver in particular is known to be vulnerable to this class of attack. As a result an application using Apache Jena SDB can be subject to RCE when connected to a malicious database server. Apache Jena SDB has been EOL since December 2020 and users should migrate to alternative options e.g. Apache Jena TDB 2.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

2 open source packages ship an affected version, including org.apache.jena:jena-sdb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.jena:jena-sdb` | Maven | All versions to 3.17.0 | None |
| `org.apache.jena:jena-sdb` | Maven | All versions to 3.17.0 | None |

Products: Apache Jena Sdb.

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

Product is end of life, replace it.

## Is CVE-2022-45136 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45136 is a critical unsafe deserialization vulnerability in Apache Jena SDB, published on 14 Nov 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-45136 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.jena:jena-sdb (Maven): affected all versions up to 3.17.0; no fix listed
- org.apache.jena:jena-sdb (Maven): affected all versions up to 3.17.0; 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-45136/ (Markdown: https://insights.sbomify.com/CVE-2022-45136/index.md)
```

## Sources

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

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