Sun SDKJDK/JRE up to 6u10 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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Sun SDKJDK and JRE up to 6u10. This vulnerability affects unknown code. This manipulation causes information disclosure. This vulnerability is handled as CVE-2008-5341. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Sun SDKJDK and JRE up to 6u10 (Programming Language Software) and classified as problematic. Affected by this vulnerability is an unknown code. 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. The summary by CVE is:

Unspecified vulnerability in Java Web Start (JWS) and Java Plug-in with Sun JDK and JRE 6 Update 10 and earlier, and JDK and JRE 5.0 Update 16 and earlier, allows untrusted JWS applications to obtain the pathname of the JWS cache and the application username via unknown vectors, aka CR 6727071.

The bug was discovered 12/03/2008. The weakness was released 12/05/2008 (Website). The advisory is shared at us-cert.gov. This vulnerability is known as CVE-2008-5341 since 12/04/2008. The exploitation appears to be easy. The attack can be launched remotely. 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.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 42834 (GLSA-200911-02 : Sun JDK/JRE: Multiple vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 185080 (HP-UX Running Java Multiple Vulnerabilities (HPSBUX02411)).

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

The vulnerability is also documented in the databases at X-Force (47055), Tenable (42834), SecurityFocus (BID 30140†), OSVDB (50511†) and Secunia (SA34233†). Entries connected to this vulnerability are available at VDB-3956, VDB-43143, VDB-43142 and VDB-43141. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Support

  • end of life (old version)

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 42834
Nessus Name: GLSA-200911-02 : Sun JDK/JRE: Multiple vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 835195
OpenVAS Name: HP-UX Update for NFS/ONCplus HPSBUX02375
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: 🔍

Timelineinfo

07/08/2008 🔍
12/03/2008 +148 days 🔍
12/03/2008 +0 days 🔍
12/04/2008 +1 days 🔍
12/05/2008 +1 days 🔍
12/05/2008 +0 days 🔍
01/21/2009 +47 days 🔍
03/11/2009 +49 days 🔍
11/17/2009 +251 days 🔍
11/18/2009 +1 days 🔍
03/17/2015 +1945 days 🔍
08/03/2021 +2331 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: us-cert.gov
Status: Not defined
Confirmation: 🔍

CVE: CVE-2008-5341 (🔍)
GCVE (CVE): GCVE-0-2008-5341
GCVE (VulDB): GCVE-100-45301

OVAL: 🔍
IAVM: 🔍

X-Force: 47055
SecurityFocus: 30140
Secunia: 34233
OSVDB: 50511 - CVE-2008-5341 - Sun - Java - Unspecified Issue
Vulnerability Center: 20572 - Java Web Start (JWS) and Java Plug-in with Sun JDK, SDK and JRE Disclosure of JWS Cache Pathname, Medium
Vupen: ADV-2008-3339

See also: 🔍

Entryinfo

Created: 03/17/2015 16:11
Updated: 08/03/2021 11:53
Changes: 03/17/2015 16:11 (79), 08/25/2019 16:18 (6), 08/03/2021 11:53 (4)
Complete: 🔍
Cache ID: 216:B4A: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 ▸

Interested in the pricing of exploits?

See the underground prices here!