Oracle Java SE 6u85/7u72/8u25 information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.3$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Oracle Java SE 6u85/7u72/8u25. Affected is an unknown function. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2015-0403. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Oracle Java SE 6u85/7u72/8u25 (Programming Language Software). It has been declared as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Unspecified vulnerability in Oracle Java SE 6u85, 7u72, and 8u25 allows local users to affect confidentiality, integrity, and availability via unknown vectors related to Deployment.

The issue has been introduced in 10/16/2014. The weakness was shared 01/20/2015 with Oracle as Oracle Critical Patch Update Advisory - January 2015 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2015-0403 since 12/17/2014. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 96 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 81491 (AIX Java Advisory : java_feb2015_advisory.asc (POODLE)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family AIX Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 185098 (HP-UX running Java6 Multiple Vulnerabilities (HPSBUX03273)).

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (100145), Tenable (81491), SecurityFocus (BID 72148†) and Vulnerability Center (SBV-48812†). Additional details are provided at blogs.oracle.com. The entries VDB-27, VDB-68712, VDB-68703 and VDB-68721 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.4
VulDB Meta Temp Score: 7.3

VulDB Base Score: 8.4
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 81491
Nessus Name: AIX Java Advisory : java_feb2015_advisory.asc (POODLE)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 100895
OpenVAS Name: Oracle Java SE JRE Multiple Unspecified Vulnerabilities-03 Feb 2015 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
ISS Proventia IPS: 🔍

Timelineinfo

10/16/2014 🔍
12/17/2014 +62 days 🔍
01/20/2015 +34 days 🔍
01/20/2015 +0 days 🔍
01/20/2015 +0 days 🔍
01/21/2015 +1 days 🔍
01/21/2015 +0 days 🔍
02/06/2015 +16 days 🔍
02/26/2015 +20 days 🔍
03/05/2022 +2564 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - January 2015
Organization: Oracle
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-0403 (🔍)
GCVE (CVE): GCVE-0-2015-0403
GCVE (VulDB): GCVE-100-68749

OVAL: 🔍

X-Force: 100145 - Oracle Java SE Deployment unspecified, Medium Risk
SecurityFocus: 72148 - Oracle Java SE CVE-2015-0403 Local Java SE Vulnerability
SecurityTracker: 1031580
Vulnerability Center: 48812 - [cpujan2015-1972971] Oracle Java SE Local Code Execution via Deployment, Medium

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 01/21/2015 11:33
Updated: 03/05/2022 09:31
Changes: 01/21/2015 11:33 (75), 06/21/2017 10:56 (9), 03/05/2022 09:28 (3), 03/05/2022 09:31 (1)
Complete: 🔍
Cache ID: 216:13A:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!