dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2015-4796

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, when running on Windows, allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors, a different vulnerability than CVE-2015-4888.

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-4796 is an unspecified vulnerability in the Java VM component of Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 running on Windows. The vulnerability allows remote authenticated users to achieve complete impact on confidentiality, integrity, and availability via unknown attack vectors. This is distinct from CVE-2015-4888 which affects the same component.

MitigationApply Oracle Critical Patch Update (CPU) released in July 2015 or later that addresses this vulnerability; ensure Oracle Database patches are applied specifically for the Java VM component on affected Windows servers.

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
WindowsOperating system
Affected:all versions

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. Confirm Oracle Database is running on Windows
    Identify the operating system hosting the Oracle Database instance using 'SELECT host_name FROM v$instance' or checking system info
    Affected if The database runs on an OS other than Windows, the vulnerability does not apply
  2. Check Oracle Database version
    Run 'SELECT version FROM v$instance' or check Oracle inventory for exact version number
    Affected if Version is NOT 11.2.0.4, 12.1.0.1, or 12.1.0.2, the system is not affected by this specific CVE
  3. Verify Java VM component is installed
    Query 'SELECT comp_name, version, status FROM dba_registry' to list installed components, or check for JVM-related packages
    Affected if Java VM component is not installed, the vulnerability cannot be exploited
  4. Check if remote authentication is enabled
    Review Oracle listener configuration and remote_login_passwordfile parameter using 'SHOW PARAMETER remote_login_passwordfile'
    Affected if Remote connections are disabled and only local authentication exists, the attack vector may not be accessible

The environment is affected only if Oracle Database 11.2.0.4, 12.1.0.1, or 12.1.0.2 is running on Windows with the Java VM component installed and remote authentication enabled.

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) released in July 2015 or later that addresses this vulnerability; ensure Oracle Database patches are applied specifically for the Java VM component on affected Windows servers.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update October 2015 or later; alternatively upgrade to Oracle Database 12.1.0.3 or later PSU

  1. 1. Identify the Oracle Critical Patch Update (CPU) that addresses CVE-2015-4796 by checking the Oracle Critical Patch Updates advisory for October 2015 or subsequent relevant CPUs
  2. 2. Navigate to Oracle Support (support.oracle.com) and search for the patch number associated with CVE-2015-4796 for your specific database version (11.2.0.4, 12.1.0.1, or 12.1.0.2)
  3. 3. Download the applicable patch from Oracle Support
  4. 4. Review the patch readme file for prerequisites and installation instructions
  5. 5. Back up the Oracle Database before applying the patch
  6. 6. Stop the Oracle Database services and listener
  7. 7. Apply the patch using OPatch (oracle-patch-utility) with the command: opatch apply
  8. 8. Start the Oracle Database services and verify the patch was applied successfully using: opatch lsinventory
Caveat Patch application may require database downtime; test thoroughly 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-4796 — 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-4796 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