dbcve.org
Datadirect Odbc Oracle Wire Protocol DriverDatabase / datastore · Progress

CVE-2023-34364

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-09
Fix available
A fix is available. Upgrade to 08.02.2770 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in Progress DataDirect Connect for ODBC Oracle driver before version 08.02.2770. The flaw is triggered by overly large values in certain connection string options, which overrun the allocated buffer and allow arbitrary code execution.

MitigationUpgrade to DataDirect Connect for ODBC version 08.02.2770 or later. Until then, restrict access to systems using the affected ODBC driver and validate connection string inputs to limit their length.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Datadirect Odbc Oracle Wire Protocol DriverDatabase / datastore
Affected:< 08.02.2770

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Progress DataDirect Oracle ODBC driver is installed
    Open Windows ODBC Data Sources (odbcad32.exe) or check for driver files in the installation directory (typically C:\Program Files\Progress\DataDirect or C:\Program Files (x86)\Progress\DataDirect). Look for DLLs named 'ddoraw32.dll' or similar Oracle Wire Protocol driver files.
    Affected if The driver is present on the system
  2. Locate the installed driver version
    In ODBC Data Source Administrator, select the driver and view properties, or right-click the driver DLL and select Properties > Details to view the File Version. Alternatively, check the version in the Windows Registry under HKLM\SOFTWARE\ODBC\ODBCINST.INI\DataDirect Oracle Wire Protocol.
    Affected if Version information cannot be determined or shows a version number
  3. Compare installed version against the fixed release
    Compare the found version number to 08.02.2770. The driver is vulnerable if the version is earlier than 08.02.2770 (for example, 08.02.2700, 08.00.2500, etc.).
    Affected if Version is less than 08.02.2770
  4. Identify configured ODBC data sources using the Oracle driver
    Open ODBC Data Source Administrator and check both User DSN and System DSN tabs for any data sources configured to use 'DataDirect Oracle Wire Protocol' driver. These data sources would accept connection strings that could trigger the overflow.
    Affected if Any data sources are configured with this driver

The environment is affected if Progress DataDirect Connect for ODBC Oracle Wire Protocol Driver is installed with a version number lower than 08.02.2770.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 08.02.2770 or later
Fixed in 08.02.2770
Interim mitigation

Upgrade to DataDirect Connect for ODBC version 08.02.2770 or later. Until then, restrict access to systems using the affected ODBC driver and validate connection string inputs to limit their length.

Recommended fix High confidence

08.02.2770 or later

  1. Identify the current version of the DataDirect Connect for ODBC Oracle Wire Protocol Driver installed on the system
  2. Navigate to the Progress Software downloads portal or contact Progress customer support to obtain version 08.02.2770 or later
  3. Uninstall the current (vulnerable) version of the DataDirect ODBC driver
  4. Install the fixed version 08.02.2770 or newer
  5. Restart any applications or services that utilize the ODBC driver
  6. Verify the new version is correctly installed by checking driver properties or using odbcad32.exe on Windows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datadirect Odbc Oracle Wire Protocol Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34364 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data