CVE-2016-0499: Critical severity oracle database vulnerability

Published Jan 21, 2016

Updated

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, a different vulnerability than CVE-2015-4794.

Affected Software

3 affected components

Oracle Database Server=11.2.0.4

Oracle Database Server=12.1.0.1

Oracle Database Server=12.1.0.2

Remediation

Patch Available

http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html

Event History

Jan 21, 2016

CVE Published

via MITRE·02:00 AM

Data Sourced

via MITRE·02:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2016-0499?

CVE-2016-0499 has not been assigned a Common Vulnerability Scoring System (CVSS) score, but it is considered critical due to its potential impact on confidentiality, integrity, and availability.

Who is affected by CVE-2016-0499?

CVE-2016-0499 affects remote authenticated users of Oracle Database Server versions 11.2.0.4, 12.1.0.1, and 12.1.0.2.

How do I fix CVE-2016-0499?

To fix CVE-2016-0499, apply the latest Oracle security patches provided in the CPU releases for the affected database versions.

What types of attacks can CVE-2016-0499 facilitate?

CVE-2016-0499 can potentially allow attackers to affect the confidentiality, integrity, and availability of the database.

Is CVE-2016-0499 related to any other vulnerabilities?

CVE-2016-0499 is distinct and a different vulnerability from CVE-2015-4794.