dbcve.org
DatabaseDatabase / datastore · Oracle

CVE-2023-21934

MEDIUM · 6.8 CVSS v3.1 Published 2023-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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
Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19c and 21c. Difficult to exploit vulnerability allows low privileged attacker having User Account privilege with network access via TLS to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java VM accessible data as well as unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).

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

Vulnerability in the Java VM component of Oracle Database Server (versions 19c and 21c) allows a low privileged attacker with network access via TLS to achieve unauthorized creation, deletion, or modification of critical data accessible to Java VM, as well as unauthorized access to critical or all Java VM data. The attack is characterized as difficult to exploit and requires existing user account credentials.

MitigationApply the latest Oracle Critical Patch Update (CPU) for Java VM in Oracle Database 19c and 21c. Additionally, restrict network access via TLS to the database and enforce least-privilege principles for user accounts.

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
DatabaseDatabase / datastore
Affected:= 19c= 21c

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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 the Oracle Database version
    Query the database with: SELECT BANNER FROM v$VERSION; or check the Oracle inventory for the installed database version.
    Affected if The version is 19c or 21c (any patch set within these release lines).
  2. Confirm Java VM component is installed
    Query: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Java%'; or check for the presence of the JAVAVM subsystem in the database.
    Affected if Java VM shows as 'VALID' or 'INSTALLED' in the registry, indicating the component is present and loaded.
  3. Verify TLS network listener is enabled
    Check the Oracle listener configuration (listener.ora) and sqlnet.ora for TLS/SSL settings. Query: SELECT VALUE FROM V$PARAMETER WHERE NAME='listener_networks'; or check if the database accepts TLS connections.
    Affected if TLS is enabled and the listener accepts network connections (the attack requires network access via TLS).
  4. Check for existing database user accounts
    Query: SELECT USERNAME FROM DBA_USERS WHERE ACCOUNT_STATUS='OPEN'; to list active user accounts.
    Affected if There are active user accounts (the attacker needs existing user account credentials to exploit this flaw).

A user is affected if they run Oracle Database 19c or 21c with Java VM installed, TLS network access enabled, and have existing user accounts that could be compromised.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Oracle Critical Patch Update (CPU) for Java VM in Oracle Database 19c and 21c. Additionally, restrict network access via TLS to the database and enforce least-privilege principles for user accounts.

Recommended fix Moderate confidence

Oracle 19c: Upgrade to latest 19c Release Update (RU). Oracle 21c: Migrate to Oracle Database 23c (21c is desupported)

  1. Check current Oracle Database version and installed patches using 'SELECT VERSION FROM V$INSTANCE;' and 'SELECT PATCH_ID, PATCH_DESCRIPTION, VERSION FROM DBA_REGISTRY_SQLPATCH;'
  2. Download and apply the latest Oracle Critical Patch Update (CPU) that addresses CVE-2023-21934 from Oracle Support (refer to Oracle Critical Patch Update Advisory for the quarter containing the fix)
  3. Alternatively, apply the latest Release Update (RU) for your version line (19c: latest 19.x RU; 21c: migrate to 23c as 21c is desupported)
  4. After patching, validate the fix is installed by re-checking DBA_REGISTRY_SQLPATCH for the security patch
  5. Restart Java VM or database services as required by the patch application
Caveat Standard Oracle patch application may require downtime and should be tested in non-production environment first

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

Fix this in Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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