Database ServerDatabase / datastore · Oracle

CVE-2020-2735

HIGH · 8.0 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 11.2.0.4, 12.1.0.2, 12.2.0.1, 18c and 19c. Difficult to exploit vulnerability allows low privileged attacker having Create Session privilege with network access via Oracle Net to compromise Java VM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java VM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java VM. CVSS 3.0 Base Score 8.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H).

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 Oracle Database's Java VM component allows a low-privileged attacker with Create Session privilege and network access to compromise Java VM through difficult-to-exploit attacks requiring human interaction. Successful exploitation leads to complete takeover of Java VM with high impacts across confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update containing the fix for CVE-2020-2735 to affected database versions (11.2.0.4, 12.1.0.2, 12.2.0.1, 18c, 19c), and restrict Java VM permissions for low-privileged users until patch is applied.

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
Database ServerDatabase / datastore
Affected:= 11.2.0.4= 12.1.0.2= 12.2.0.1= 18c= 19c

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/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. Identify Oracle Database version
    Query the database version using SELECT VERSION FROM V$INSTANCE; or check oracle inventory for installed database versions
    Affected if version matches 11.2.0.4, 12.1.0.2, 12.2.0.1, 18c, or 19c
  2. Confirm Java VM component is installed
    Query DBA_REGISTRY or check if Java VM options are present: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Java%';
    Affected if Java VM component is installed and present in the registry
  3. Verify Java VM is enabled and accessible
    Check if Java VM is loaded in the database: SELECT * FROM V$OPTION WHERE PARAMETER = 'Java';
    Affected if Java VM returns as enabled/true
  4. Identify users with Create Session privilege
    Query DBA_TAB_PRIVS or ROLE_TAB_PRIVS for users granted Create Session: SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE PRIVILEGE='CREATE SESSION';
    Affected if low-privileged users exist with only Create Session privilege and network access
  5. Assess network exposure of Java VM
    Review listener.ora and SQL*Net configuration to determine if Java VM is exposed over network interfaces
    Affected if database listener accepts network connections from untrusted networks

Environment is affected if running an affected Oracle Database version (11.2.0.4, 12.1.0.2, 12.2.0.1, 18c, or 19c) with Java VM installed and enabled, and low-privileged users with Create Session privilege can access the database over the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update containing the fix for CVE-2020-2735 to affected database versions (11.2.0.4, 12.1.0.2, 12.2.0.1, 18c, 19c), and restrict Java VM permissions for low-privileged users until patch is applied.

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-2735 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