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

CVE-2023-34363

MEDIUM · 5.9 CVSS v3.1 Published 2023-06-09
Fix available
A fix is available. Upgrade to 08.02.2770 or later.
See remediation →
68/100
Remediation priority · Elevated
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
An issue was discovered in Progress DataDirect Connect for ODBC before 08.02.2770 for Oracle. When using Oracle Advanced Security (OAS) encryption, if an error is encountered initializing the encryption object used to encrypt data, the code falls back to a different encryption mechanism that uses an insecure random number generator to generate the private key. It is possible for a well-placed attacker to predict the output of this random number generator, which could lead to an attacker decrypting traffic between the driver and the database server. The vulnerability does not exist if SSL / TLS encryption is used.

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

In Progress DataDirect Connect for ODBC for Oracle versions before 08.02.2770, when Oracle Advanced Security (OAS) encryption encounters an error during encryption object initialization, the code falls back to an alternative encryption mechanism that uses a cryptographically insecure random number generator. Attackers who can predict or reconstruct the RNG output can decrypt captured traffic between the driver and database server.

MitigationUpgrade to DataDirect Connect for ODBC version 08.02.2770 or later; alternatively, configure the connection to use SSL/TLS encryption instead of OAS encryption, as the vulnerability does not exist when SSL/TLS is used.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Identify DataDirect Oracle ODBC driver installation
    Locate the DataDirect Connect for ODBC driver files for Oracle. On Windows, check the ODBC Data Source Administrator ( Drivers tab) or the installation directory (typically C:\Progress\DataDirect\Connect_for_ODBC_82\). On Linux/Unix, check /opt/datadirect/connect_for_odbc/ or the product documentation for installation path.
    Affected if The DataDirect Oracle ODBC driver is present on the system
  2. Determine installed driver version
    Open the ODBC Driver configuration or check the driver file properties. On Windows, right-click the driver DLL (oraoracle.dll or similar) and view Properties > Details > File Version. Alternatively, query the driver through ODBC administration or check the DataDirect release notes or installer.
    Affected if The version number is lower than 08.02.2770
  3. Verify Oracle Advanced Security (OAS) encryption is enabled
    Check the ODBC data source configuration or connection string for the Oracle connection. Look for OAS-related encryption settings such as 'EncryptionMethod=OAS' or similar OAS encryption parameters in the DSN configuration or connection string. This is distinct from SSL/TLS encryption.
    Affected if OAS encryption method is configured and enabled for the Oracle connection (not using SSL/TLS)

The system is affected if the DataDirect Oracle ODBC driver version is below 08.02.2770 AND Oracle Advanced Security (OAS) encryption is enabled for any Oracle connection, as this combination allows the insecure fallback encryption to trigger under error conditions.

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; alternatively, configure the connection to use SSL/TLS encryption instead of OAS encryption, as the vulnerability does not exist when SSL/TLS is used.

Recommended fix High confidence

08.02.2770 or later

  1. Upgrade the DataDirect ODBC Oracle Wire Protocol Driver to version 08.02.2770 or later
  2. Alternatively, if upgrading is not immediately possible, ensure SSL/TLS encryption is used instead of Oracle Advanced Security (OAS) encryption - this completely mitigates the vulnerability

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34363 — 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-34363 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