# CVE-2023-34364: Memory corruption in n/a

> A buffer overflow in the ODBC driver allows attackers to execute arbitrary code on the host via a malicious connection string.

- **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:** 9 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-q2w3-vxgc-67jq

## What is CVE-2023-34364?

CVE-2023-34364 is a critical memory corruption vulnerability in n/a, published on 9 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow was discovered in Progress DataDirect Connect for ODBC before 08.02.2770 for Oracle. An overly large value for certain options of a connection string may overrun the buffer allocated to process the string value. This allows an attacker to execute code of their choice on an affected host by copying carefully selected data that will be executed as code.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Progress Datadirect Odbc Oracle Wire Protocol Driver.

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

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

## Is CVE-2023-34364 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34363](https://insights.sbomify.com/CVE-2023-34363/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34364 is a critical memory corruption vulnerability in n/a, published on 9 Jun 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-2023-34364 in the wild and no public exploit code.

Affected product: n/a. 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-2023-34364/ (Markdown: https://insights.sbomify.com/CVE-2023-34364/index.md)
```

## Sources

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

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