dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2015-4794

HIGH · 9.0 CVSS v2.0 Published 2015-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Unspecified vulnerability in the Java VM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors.

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 · moderate confidence

CVE-2015-4794 is an unspecified vulnerability in the Java VM component of Oracle Database Server affecting versions 11.2.0.4, 12.1.0.1, and 12.1.0.2. The vulnerability allows remote authenticated users to impact confidentiality, integrity, and availability through unknown vectors related to Java VM execution within the database environment.

MitigationApply Oracle Critical Patch Updates (CPUs) that address this vulnerability, or if Java VM is not required in the database environment, consider disabling it to reduce the attack surface. Implement network segmentation and enforce least-privilege access principles for database users.

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.1= 12.1.0.2

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
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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. Check Oracle Database Server version
    Execute SELECT version FROM v$instance; or SELECT * FROM v$version; to obtain the exact database version
    Affected if The version matches 11.2.0.4, 12.1.0.1, or 12.1.0.2 exactly
  2. Verify Java VM component is installed
    Query SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Java%'; or check SELECT * FROM v$option WHERE parameter = 'Java';
    Affected if Java VM component shows as INSTALLED or VALID in the registry
  3. Confirm Java VM is enabled and usable
    Execute SELECT dbms_java.long_name('test') FROM dual; or test by checking if Java classes can be loaded. Also check SELECT * FROM dba_objects WHERE object_type = 'JAVA CLASS';
    Affected if Java VM responds to queries and Java objects are accessible, indicating the component is active
  4. Check if Java VM is actually in use
    Review database for Java stored procedures, Java classes, or JVM-related objects by querying dba_objects with object_type like 'JAVA%'
    Affected if Any Java objects exist in the database, confirming Java VM execution context is present

You are affected if your Oracle Database version is exactly 11.2.0.4, 12.1.0.1, or 12.1.0.2 AND the Java VM component is installed and usable in your environment.

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 Updates (CPUs) that address this vulnerability, or if Java VM is not required in the database environment, consider disabling it to reduce the attack surface. Implement network segmentation and enforce least-privilege access principles for database users.

Recommended fix High confidence

For 12.1.0.2, upgrade to 12.1.0.3; for 11.2.0.4 and 12.1.0.1, apply Oracle patch from October 2015 CPU

  1. Apply the October 2015 Critical Patch Update (CPU) from Oracle Support
  2. Navigate to Oracle Support and search for patch 21364635 (or the applicable patch for CVE-2015-4794)
  3. Download the appropriate patch for your Oracle Database version (11.2.0.4, 12.1.0.1, or 12.1.0.2)
  4. Stop all Oracle Database services using srvctl or sqlplus
  5. Apply the patch using opatch apply following Oracle's documentation
  6. Restart Oracle Database services after successful patch application
  7. Verify the patch was applied by querying V$PATCHES or checking opatch lsinventory
Caveat Patches are cumulative in Oracle CPUs; test in non-production environment before applying to production

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

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-2015-4794 — 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-2015-4794 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