CVE-2024-21093
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 · uneditedVulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.22 and 21.3-21.13. Difficult to exploit vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via Oracle Net to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 confidenceThis is an authorization bypass vulnerability in Oracle Database's Java VM component. A low-privileged attacker with Create Session and Create Procedure database privileges can exploit this over the network via Oracle Net to gain unauthorized access to critical data or complete access to all Java VM accessible data. The attack complexity is high, but requires no user interaction.
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>= 19.3, <= 19.22>= 21.3, <= 21.13CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Java VM component is installedRun: SELECT comp_id, comp_name, version, status FROM dba_registry WHERE comp_id = 'JAVAVM'; If no rows returned, Java VM is not installed.Affected if The query returns a row with status as VALID, meaning Java VM is present in this Oracle Database installation.
-
Determine installed Oracle Database versionRun: SELECT version FROM v$instance; Compare the returned version against the affected ranges: 19.3 through 19.22, and 21.3 through 21.13.Affected if The version falls within 19.3-19.22 or 21.3-21.13, indicating the Java VM version is vulnerable.
-
Identify users with Create Session privilegeRun: SELECT grantee, granted_role FROM dba_role_privs WHERE granted_role = 'CONNECT' OR SELECT username FROM dba_users WHERE profile != 'DEFAULT'; Review which low-privileged accounts have network access.Affected if Many user accounts exist with Create Session privilege, increasing the attack surface.
-
Identify users with Create Procedure privilegeRun: SELECT grantee, privilege FROM dba_sys_privs WHERE privilege = 'CREATE PROCEDURE'; Also check: SELECT grantee, granted_role FROM dba_role_privs WHERE granted_role = 'RESOURCE';Affected if Low-privileged application users or roles have Create Procedure privilege, which is required for the exploit.
-
Check Oracle Net listener network exposureReview the listener.ora and sqlnet.ora configuration files for listener binding addresses. Run: lsnrctl status LISTENER and check the Listening Endpoints Summary for the protocol and address.Affected if The listener is bound to a non-loopback address (0.0.0.0 or actual IP) and is accessible from outside the trusted network, making remote exploitation possible.
A user is affected if they run Oracle Database with Java VM installed, their version falls within 19.3-19.22 or 21.3-21.13, and the database is accessible over Oracle Net to users who have both Create Session and Create Procedure privileges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Oracle Critical Patch Update (CPU) that addresses this vulnerability. For affected versions 19.3-19.22 and 21.3-21.13, apply the corresponding patch. If immediate patching is not possible, restrict network access to Oracle Net listener and limit Create Session/Create Procedure privileges to only necessary users.
Apply the latest Oracle Critical Patch Update (CPU) for your respective version (19.23+ or 21.14+); alternatively, upgrade to Oracle Database 19.23 or later / 21.14 or later
- Apply the latest Oracle Critical Patch Update (CPU) that addresses CVE-2024-21093. Oracle releases CPUs quarterly (January, April, July, October).
- To obtain the appropriate patch: 1) Go to Oracle Support (support.oracle.com) 2) Search for CVE-2024-21093 or the relevant Oracle CPU advisory 3) Download and apply the patch for your specific Oracle Database version (19.3-19.22 or 21.3-21.13)
- Before applying the patch in production, test thoroughly in a non-production environment to ensure compatibility with your specific configuration.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21093 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21093 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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