# CVE-2023-32697: Sqlite-jdbc vulnerable to remote code execution when JDBC url is attacker controlled

> Attackers can execute arbitrary code if they control the JDBC URL used by applications relying on the SQLite JDBC library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Yes
- **Published:** 23 May 2023
- **Updated:** 5 Mar 2025
- **Also known as:** DEBIAN-CVE-2023-32697, GHSA-6phf-6h5g-97j2, OESA-2023-1792, UBUNTU-CVE-2023-32697

## What is CVE-2023-32697?

CVE-2023-32697 is a high-severity code injection vulnerability in xerial sqlite-jdbc, published on 23 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQLite JDBC is a library for accessing and creating SQLite database files in Java. Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. This issue impacting versions 3.6.14.1 through 3.41.2.1 and has been fixed in version 3.41.2.2.

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

## Which versions are affected by CVE-2023-32697?

2 open source packages ship an affected version, including org.xerial:sqlite-jdbc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.xerial:sqlite-jdbc` | Maven | From 3.6.14.1 | 3.41.2.2 |
| `org.xerial:sqlite-jdbc` | Maven | From 3.6.14.1 | 3.41.2.2 |

Products: Sqlite Jdbc Project Sqlite Jdbc.

## How do I fix CVE-2023-32697?

Upgrade org.xerial:sqlite-jdbc to 3.41.2.2 or later.

## Is CVE-2023-32697 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/xerial__sqlite-jdbc_CVE-2023-32697_3-41-2-1 (github_poc): https://github.com/shoucheng3/xerial__sqlite-jdbc_CVE-2023-32697_3-41-2-1

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32697 and fix it if it is affected.

What it is: CVE-2023-32697 is a high-severity code injection vulnerability in xerial sqlite-jdbc, published on 23 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32697 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.xerial:sqlite-jdbc (Maven): affected from 3.6.14.1; fixed in 3.41.2.2
- org.xerial:sqlite-jdbc (Maven): affected from 3.6.14.1; fixed in 3.41.2.2

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-2023-32697/ (Markdown: https://insights.sbomify.com/CVE-2023-32697/index.md)
```

## Sources

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

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