dbcve.org
Java Virtual MachineApplication · Oracle

CVE-2021-35619

HIGH · 7.1 CVSS v3.1 Published 2021-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/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 12.1.0.2, 12.2.0.1, 19c and 21c. Difficult to exploit vulnerability allows low privileged attacker having Create Procedure privilege with network access via Oracle Net to compromise Java VM. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Java VM. CVSS 3.1 Base Score 7.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/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 Procedure privilege to compromise Java VM via Oracle Net. Successful exploitation enables full takeover of Java VM. Requires human interaction and network access.

MitigationApply Oracle Critical Patch Update (CPU) addressing CVE-2021-35619. If Java VM is unused, consider disabling it. Review and restrict Create Procedure privilege to essential users only.

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
Java Virtual MachineApplication
Affected:= 12.1.0.2= 12.2.0.1= 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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. Identify Oracle Database version
    Query V$VERSION or execute: SELECT BANNER FROM V$VERSION; Compare the output to affected versions 12.1.0.2, 12.2.0.1, 19c, or 21c.
    Affected if Database version matches one of the four affected versions listed in the CVE.
  2. Check if Java VM component is installed
    Query DBA_REGISTRY: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Java%'; or check USER_OBJECTS for JAVA$ classes.
    Affected if Java VM appears in the registry with any status (VALID, INVALID, or not listed means not installed).
  3. Verify if Java VM is actually enabled and usable
    Attempt to compile a simple Java class: CREATE OR REPLACE JAVA SOURCE NAMED "TestJava" AS public class TestJava { }; If it compiles without error, Java VM is enabled.
    Affected if Java source compiles successfully, indicating Java VM is active and exploitable.
  4. Confirm Oracle Net (listener) is accessible
    Check if the database listener is running: LSNRCTL STATUS or TNSPING <service_name>. Verify network listeners accept connections.
    Affected if Listener is active and accepts remote connections - required for the Oracle Net attack vector.
  5. Check for Create Procedure privilege
    Query: SELECT * FROM USER_SYS_PRIVS WHERE PRIVILEGE = 'CREATE PROCEDURE'; Or request DBA to run: SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'CREATE PROCEDURE';
    Affected if Current user or any database user has been granted CREATE PROCEDURE privilege.

Environment is affected if running Oracle Database 12.1.0.2/12.2.0.1/19c/21c with Java VM installed and enabled, the listener is network-accessible, and a user possesses Create Procedure privilege.

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 Oracle Critical Patch Update (CPU) addressing CVE-2021-35619. If Java VM is unused, consider disabling it. Review and restrict Create Procedure privilege to essential users only.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update containing the fix for CVE-2021-35619; for 19c and 21c, ensure you are on the latest RU (Release Update) or RUR (Release Update Revision) that includes this security fix

  1. Check Oracle's Critical Patch Update (CPU) advisories for CVE-2021-35619 at https://www.oracle.com/security-alerts/
  2. Download and apply the relevant patch for your Oracle Database version (12.1.0.2, 12.2.0.1, 19c, or 21c) from Oracle Support
  3. Apply the patch following Oracle's standard patch application procedures
  4. After patching, verify the Java VM component is updated by checking the version or running diagnostics
  5. Restart the Oracle Database instance as required by the patch
Caveat Review Oracle patch documentation for any post-patch steps or required configuration changes; standard CPU patches typically do not introduce breaking changes

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

Fix this in Java Virtual Machine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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