Sun JRE/JDK 1.5.0 memory corruption

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.
8.8$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Sun JRE and JDK. Affected is an unknown function. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2009-3868. Furthermore, there is an exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Sun JRE and JDK (Programming Language Software). This affects an unknown functionality. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Sun Java SE in JDK and JRE 5.0 before Update 22, JDK and JRE 6 before Update 17, SDK and JRE 1.3.x before 1.3.1_27, and SDK and JRE 1.4.x before 1.4.2_24 does not properly parse color profiles, which allows remote attackers to gain privileges via a crafted image file, aka Bug Id 6862970.

The weakness was shared 11/05/2009 by Peter Vreugdenhil (regenrecht) with iDEFENSE (Website). The advisory is shared at vupen.com. This vulnerability is uniquely identified as CVE-2009-3868. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.

A public exploit has been developed in Java. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. 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. The commercial vulnerability scanner Qualys is able to test this issue with plugin 185067 (HP-UX Running Java, Multiple Vulnerabilities (HPSBUX02503)).

Upgrading to version 1.6.0 eliminates this vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 8404.

The vulnerability is also documented in the databases at Tenable (42834), SecurityFocus (BID 36881†), Secunia (SA37386†), SecurityTracker (ID 1023132†) and Vulnerability Center (SBV-23985†). The entries VDB-3956, VDB-4206, VDB-43143 and VDB-43142 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

Support

  • end of life (old version)

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 8.8

VulDB Base Score: 9.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍

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: 🔍

OpenVAS ID: 835225
OpenVAS Name: HP-UX Update for Java HPSBUX02503
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: JRE/JDK 1.6.0
TippingPoint: 🔍

Timelineinfo

10/29/2009 🔍
10/29/2009 +0 days 🔍
11/05/2009 +6 days 🔍
11/05/2009 +0 days 🔍
11/05/2009 +0 days 🔍
11/11/2009 +6 days 🔍
03/18/2015 +1953 days 🔍
04/07/2025 +3673 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: vupen.com⛔
Researcher: Peter Vreugdenhil (regenrecht)
Organization: iDEFENSE
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2009-3868 (🔍)
GCVE (CVE): GCVE-0-2009-3868
GCVE (VulDB): GCVE-100-50709

OVAL: 🔍

SecurityFocus: 36881 - Sun Java SE November 2009 Multiple Security Vulnerabilities
Secunia: 37386
SecurityTracker: 1023132
Vulnerability Center: 23985 - Sun Java SE in JDK, JRE and SDK Privilege Escalation Vulnerability Related to Color Profiles Parsing, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/18/2015 15:15
Updated: 04/07/2025 14:15
Changes: 03/18/2015 15:15 (63), 02/16/2017 10:20 (14), 08/27/2021 08:10 (4), 08/27/2021 08:12 (1), 02/02/2025 03:34 (18), 04/07/2025 14:15 (1)
Complete: 🔍
Cache ID: 216::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 ▸

Want to know what is going to be exploited?

We predict KEV entries!